Apparatus and method for changing, adding and deleting a job, and a storage medium for such a program

ABSTRACT

A job is selected from a job list, and is either copied or is extracted from a job storage unit. The job, or the copy, is transmitted to a designated destination. A transmission job or a printing job is stored in conjunction with a corresponding execution time in the job storage unit, so that a job can be selected from the job list and the execution time for the selected job can be changed. Further, the jobs stored in the print queue are displayed as a list, and a selected job is moved from the print queue to the job storage unit, so that the printing of the job in the print queue can be performed. In addition, the histories of jobs that were executed are displayed as a list, so that a specific job can be selected and re-executed. Furthermore, a process that is performed is managed for the user who instructed the process. When logout is instructed, management data are examined in order to determine whether there is an unprocessed job that was previously instructed by the user. If an unprocessed job is found, the user is notified. If the operator is a manager, a menu is displayed so that all the jobs in the print queue can be deleted. When jobs are deleted, the owners of the individual jobs are notified. Furthermore, a job that is to be published is selected from the job list and a publication time limit is set. Then, the selected job, accompanied by its publication time limit, is added to the published information list. The publication time limits for all the jobs included in the list are examined, and the jobs for which the publication time limits have not yet expired are displayed. As a result, the published information can be read or printed by another apparatus.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to an information processing apparatus andmethod for changing, adding and deleting a job, such as the transmissionor the printing of information, and a storage medium on which such aprogram is stored.

2. Related Background Art

Conventionally, printing is performed by a host information processingapparatus, for example, transmitting a print job to a printer. In thiscase, the host apparatus transmits a job that it can not execute to anapparatus that can execute that job. However, if a transmission sourceapparatus and a destination apparatus can both execute the same job, andif it is desired that the same job be executed by both theseapparatuses, the transmission source apparatus must create two jobs: onejob to be transmitted and another job to be executed by the sourceapparatus.

Conventionally, the transmission of information is performed in responseto a user issuing a transmission instruction for a transmission to beeffected at a desired transmission time. Transmission of information isalso performed at a transmission time that is designated in advance.However, once the transmission setup is completed, the setup can not bechanged. In addition, another transmission process can not be set up forinformation for which the transmission has been set up.

For the printing of information, conventionally, print information istransmitted toga print queue, and information stored in the print queueis then printed. However, the print setup for specific information inthe print queue can not be changed. When printing is to be performed ata desired time, a print instruction must be issued for that time inorder for the printing to be executed.

A conventional information processing apparatus stores the history ofprocesses that have been performed, and refers to this history asneeded. However, the history is not referred to more often than theconfirmation of an activity and the re-entry of a command are performed.

A conventional information processing apparatus, a printer, for example,executes printing when a user operates a computer and issues a printinstruction to the printer. When the printing is completed, the issues aprint end notification to the apparatus that instructed the printing.

Even in a system in which a print end notification is issued, however, auser may forget that an instruction has not yet been executed, or evenwhether the instruction has been completed. In this case, the user mayterminate the processing without being aware that there is a processthat has not yet been performed. Furthermore, when a user moves awayfrom the computer through which the print instruction was issued, theuser will not be aware of the statuses of the apparatus and of theprocess, and will not be able to control the execution of the process.

Conventionally, in an environment wherein a plurality of users employthe same resources by using the same apparatus or employ the sameresources across a network, an authority greater that given to a commonuser is provided for the manager of the information processing apparatusin order to provide management control for resources employed by aplurality of users. Therefore, for the management of an apparatus, themanager can perform various functions that the common users can not.

Further, a conventional computer identifies a user during the logging-inprocess, or provides a password to be used when a user desires to accessa file in order to permit the limited reading of stored information.However, as specific information stored in specific apparatuses can notbe published, such information can not be read by another apparatus. Inparticular, it is impossible for such information to be freely readduring a specified period of time, and the material can not be referredto after the time period has expired.

SUMMARY OF THE INVENTION

It is, therefore, one objective of the present invention to provide anapparatus and a method for enabling object information to be processed,to be maintained or to be deleted, as desired, when the information istransmitted.

It is another objective of the present invention to provide an apparatusand a method for changing an information transmission setup, such as atransmission time, that has previously been designated.

It is an additional objective of the present invention to provide anapparatus and a method for setting a time for the printing ofinformation, and for changing a print setup that has previously beendesignated.

It is a further objective of the present invention to provide anapparatus and a method with which it is easy to change objectinformation for a process that was previously performed to objectinformation for another process.

It is still another objective of the present invention to provide anapparatus and a method for detecting, at a predetermined time, thepresence of a process that has been instructed by a user and that hasnot yet been performed.

It is a still additional objective of the present invention to providean apparatus and a method for publishing specific information stored ina specific apparatus so that another user can read it.

To achieve the above objectives, according to one aspect of the presentinvention, an information processing apparatus comprises:

transmission means for transmitting object information that is to beprocessed;

object information storage means for storing the object information thatis to be processed;

display means for displaying as a list the object information that isstored in the object information storage means;

object information selection means for selecting object information fromthe list of object information;

destination designation means for designating a transmission destinationfor the object information that is to be processed;

transmission method selection means for selecting a first transmissionmethod or a second transmission method; and

control means for, when the first transmission method is selected by thetransmission method selection means, permitting the transmission meansto copy from the object information storage means the object informationselected by the object information selection means, and, when the secondtransmission method is selected by the transmission method selectionmeans, for permitting the transmission means to extract, from the objectinformation storage means, the object information that is selected bythe object information selection means, and to transmit the objectinformation to the transmission destination that is designated by thetransmission designation destination means.

According to one more aspect of the present invention, an informationprocessing method comprises:

a display step of displaying, as a list, object information that isstored in an object information storage unit for storing the objectinformation that is to be processed;

an object information selection step of selecting object informationfrom the list of object information;

a destination designation step of designating a transmission destinationfor the object information that is to be processed;

a transmission method selection step of selecting a first transmissionmethod or a second transmission method; and

a transmission step of, when the first transmission method is selectedat the transmission method selection step, copying from the objectinformation storage unit the object information selected at the objectinformation selection step, and of, when the second transmission methodis selected at the transmission method selection step, extracting fromthe object information storage unit the object information that isselected at the object information selection step, and transmitting theobject information to the transmission destination that is designated atthe transmission designation destination step.

According to another aspect of the present invention, provided is astorage medium on which is stored a program, which comprises:

a display step of displaying, as a list, object information that isstored in an object information storage unit for storing the objectinformation that is to be processed;

an object information selection step of selecting object informationfrom the list of object information;

a destination designation step of designating a transmission destinationfor the object information that is to be processed;

a transmission method selection step of selecting a first transmissionmethod or a second transmission method; and

a transmission step of, when the first transmission method is selectedat the transmission method selection step, copying from the objectinformation storage unit the object information selected at the objectinformation selection step, and of, when the second transmission methodis selected at the transmission method selection step, extracting fromthe object information storage unit the object information that isselected at the object information selection step, and transmitting theobject information to the transmission destination that is designated atthe transmission designation destination step.

According to an additional aspect of the present invention, aninformation processing apparatus comprises:

transmission means for transmitting object information that is to beprocessed;

object information storage means for storing the object information inconjunction with a corresponding execution time and a correspondingtransmission destination;

display means for displaying as a list object information that is storedin the object information storage means;

object information selection means for selecting object information fromthe object information list;

change means for changing a setup that is stored in the objectinformation storage means in conjunction with the object informationselected by the object information selection means; and

control means for permitting the transmission means to transmit theobject information, which is stored in the object information storagemeans, to the transmission destination and at the execution time thatare stored in the object information storage means in conjunction withthe object information.

According to a further aspect of the present invention, an informationprocessing method comprises:

a display step of displaying as a list object information that is storedin an object information storage unit for storing the object informationin conjunction with a corresponding execution time and a correspondingtransmission destination;

an object information selection step of selecting object informationfrom the object information list;

a change step of changing a setup that is stored in the objectinformation storage unit in conjunction with the object informationselected at the object information selection step; and

a transmission step of transmitting the object information, which isstored in the object information storage unit, to the transmissiondestination and at the execution time that are stored in the objectinformation storage unit in conjunction with the object information.

According to one further aspect of the present invention, provided is astorage medium on which is stored a program, which comprises:

a display step of displaying as a list object information that is storedin an object information storage unit for storing the object informationin conjunction with a corresponding execution time and a correspondingtransmission destination;

an object information selection step of selecting object informationfrom the object information list;

a change step of changing a setup that is stored in the objectinformation storage unit in conjunction with the object informationselected at the object information selection step; and

a transmission step of transmitting the object information, which isstored in the object information storage unit, to the transmissiondestination and at the execution time that are stored in the objectinformation storage unit in conjunction with the object information.

According to yet one more aspect of the present invention, aninformation processing apparatus comprises:

print queue storage means for storing object information to be printed;

printing means for printing the object information stored in the printqueue storage means;

object information storage means for storing object information inconjunction with time information specifying a printing time for theobject information;

transfer means for transferring the object information from the objectinformation storage means to the print queue storage means in accordancewith the time information that is stored in the object informationstorage means in conjunction with the object information;

display means for displaying as a list the object information that isstored in the print queue storage means;

object information selection means for selecting object information fromthe object information list; and

moving means for moving, from the print queue storage means to theobject information storage means, the object information that isselected by the object information selection means.

According to yet another aspect of the present invention, an informationprocessing method comprises:

a printing step of printing object information that is stored in a printqueue for storing object information to be printed;

an object information storage step for storing object information;

a transfer step of transferring the object information, which is storedin an object information storage unit in conjunction with timeinformation specifying a printing time for the object information, tothe print queue in accordance with the time information that is storedin conjunction with the object information;

a display step of displaying as a list the object information that isstored in the print queue;

an object information selection step of selecting object informationfrom the object information list; and

a moving step of moving, from the print queue to the object informationstorage unit, the object information that is selected at the objectinformation selection step.

According to yet an additional aspect of the present invention, providedis a storage medium on which is stored a program, which comprises:

a printing step of printing object information that is stored in a printqueue for storing object information to be printed;

an object information storage step for storing object information;

a transfer step of transferring the object information, which is storedin an object information storage unit in conjunction with timeinformation specifying a printing time for the object information, tothe print queue in accordance with the time information that is storedin conjunction with the object information;

a display step of displaying as a list the object information that isstored in the print queue;

an object information selection step of selecting object informationfrom the object information list; and

a moving step of moving, from the print queue to the object informationstorage unit, the object information that is selected at the objectinformation selection step.

According to yet a further aspect of the present invention, aninformation processing apparatus comprises:

printing means for printing object information that is to be processed;

object information storage means for storing the object information inconjunction with a corresponding execution time;

display means for displaying as a list object information that is storedin the object information storage means;

object information selection means for selecting object information fromthe object information list;

change means for changing the execution time that is stored in theobject information storage means in conjunction with the objectinformation selected by the object information selection means; and

control means for permitting the printing means to print the objectinformation stored in the object information storage means at theexecution time that is stored therein in conjunction with the objectinformation.

According to yet one further aspect of the present invention, aninformation processing method comprises:

a printing step of printing object information that is to be processed;

a display step of displaying as a list object information that is storedin an object information storage unit for storing the object informationin conjunction with a corresponding execution time;

an object information selection step of selecting object informationfrom the object information list;

a change step of changing the execution time that is stored in theobject information storage unit in conjunction with the objectinformation selected at the object information selection step; and

a control step of performing the printing step so that the objectinformation stored in the object information storage unit is printed atthe execution time that is stored therein in conjunction with the objectinformation.

According to still one more aspect of the present invention, provided isa storage medium on which is stored a program, which comprises:

a printing step of printing object information that is to be processed;

a display step of displaying as a list object information that is storedin an object information storage unit for storing the object informationin conjunction with a corresponding execution time;

an object information selection step of selecting object informationfrom the object information list;

a change step of changing the execution time that is stored in theobject information storage unit in conjunction with the objectinformation selected at the object information selection step; and

a control step of performing the printing step so that the objectinformation stored in the object information storage unit is printed atthe execution time that is stored therein in conjunction with the objectinformation.

According to still another aspect of the present invention, aninformation processing apparatus comprises:

execution means for performing a process;

history storage means for storing, as a process history, the type ofprocess that is performed and object information;

list display means for displaying as a list process histories that arestored in the history storage means;

history selection means for selecting a process history from the list;and

re-execution control means for permitting the execution means to againexecute a process related to the history selected by the historyselection means.

According to still an additional aspect of the present invention, aninformation processing method comprises:

an execution step of performing a process;

a history storage step of storing the type of process that is performedand object information as a process history in a history storage unit;

a list display step of displaying as a list process histories that arestored in the history storage unit;

a history selection step of selecting a process history from the list;and

a re-execution step of again executing a process related to the historyselected at the history selection step.

According to still a further aspect of the present invention, providedis a storage medium on which is stored a program, which comprises:

an execution step of performing a process;

a history storage step of storing the type of process that is performedand object information as a process history in a history storage unit;

a list display step of displaying as a list process histories that arestored in the history storage unit;

a history selection step of selecting a process history from the list;and

a re-execution step of again executing a process related to the historyselected at the history selection step.

According to still one further aspect of the present invention, aninformation processing apparatus comprises:

history storage means for storing the type of process that is performedand object information;

list display means for displaying as a list process histories that arestored in the history storage means;

deletion instruction means for selecting a history from the list and forissuing an instruction to delete the history from the history storagemeans;

determination means for determining whether object information that isrelated to the history instructed by the deletion instruction means isstored in the history storage means in conjunction with the name ofanother user whose name differs from that of the user who issued theinstruction; and

deletion means for, when the object information is stored in conjunctionwith the name of the other user, deleting from the history storage meansa portion that is related to the user who issued the instruction todelete the history, and for, when the object information is not storedin conjunction with the name of the other user, deleting from thehistory storage means the object information that is related to thehistory for which deletion is instructed.

According to again one more aspect of the present invention, aninformation processing method comprises:

a history storage step of storing in a history storage unit the type ofprocess that is performed and object information;

a list display step of displaying as a list process histories that arestored in the history storage unit;

a deletion instruction step of selecting a history from the list and ofissuing an instruction to delete the history from the history storageunit;

a determination step of determining whether object information that isrelated to the history instructed at the deletion instruction step isstored in the history storage unit in conjunction with the name ofanother user whose name differs from that of the user who issued theinstruction; and

a deletion step of, when the object information is stored in conjunctionwith the name of the other user, deleting from the history storage unita portion that is related to the user who issued the instruction todelete the history, and of, when the object information is not stored inconjunction with the name of the other user, deleting from the historystorage unit the object information that is related to the history forwhich deletion is instructed.

According to again another aspect of the present invention, provided isa storage medium on which is stored a program, which comprises:

a history storage step of storing in a history storage unit the type ofprocess that is performed and object information;

a list display step of displaying as a list process histories that arestored in the history storage unit;

a deletion instruction step of, selecting a history from the list and ofissuing an instruction to delete the history from the history storageunit;

a determination step of determining whether object information that isrelated to the history instructed at the deletion instruction step isstored in the history storage unit in conjunction with the name ofanother user whose name differs from that of the user who issued theinstruction; and

a deletion step of, when the object information is stored in conjunctionwith the name of the other user, deleting from the history storage unita portion that is related to the user who issued the instruction todelete the history, and of, when the object information is not stored inconjunction with the name of the other user, deleting from the historystorage unit the object information that is related to the history forwhich deletion is instructed.

According to again an additional aspect of the present invention, aninformation processing apparatus comprises:

management means for managing a process to be completed incorrespondence with a user who has entered an instruction for theprocess;

instruction means for issuing a predetermined instruction;

determination means for referring to the management means to determinewhether the performance of a process that has previously been instructedby the user continues not to have been performed; and

notification means for, when the determination means determines thatthere is a process that has not yet been performed, transmitting to theuser a notification to that effect.

According to again a further aspect of the present invention, aninformation processing apparatus comprises:

acceptance means for accepting an inquiry from an external apparatusconcerning the status of an apparatus currently employed by a user; and

execution means for performing a process that corresponds to the inquiryaccepted by the acceptance means.

According to again one further aspect of the present invention, aninformation processing method comprises:

a management step of managing a process to be completed incorrespondence with a user who has entered an instruction for theprocess;

an instruction step of issuing a predetermined instruction;

a determination step of referring to data managed at the management stepto determine whether the performance of a process that has previouslybeen instructed by the user continues not to have been performed; and

a notification step of, when the determination means determines thatthere is a process that has not yet been performed, transmitting to theuser a notification to that effect.

According also to one more aspect of the present invention, aninformation processing method comprises:

an acceptance step of accepting an inquiry from an external apparatusconcerning the status of a method currently employed by a user; and

an execution step of performing a process that corresponds to theinquiry accepted at the acceptance step.

According also to another aspect of the present invention, provided is astorage medium on which is stored a program, which comprises:

a management step of managing a process to be completed incorrespondence with a user who has entered an instruction for theprocess;

an instruction step of issuing a predetermined instruction;

a determination step of referring to data managed at the management stepto determine whether the performance of a process that has previouslybeen instructed by the user continues not to have been performed; and

a notification step of, when the determination means determines thatthere is a process that has not yet been performed, transmitting to theuser a notification to that effect.

According also to an additional aspect of the present invention,provided is a storage medium on which is stored a program, whichcomprises:

an acceptance step of accepting an inquiry from an external apparatusconcerning the status of a method currently employed by a user; and

an execution step of performing a process that corresponds to theinquiry accepted at the acceptance step.

According also to a further aspect of the present invention, aninformation processing apparatus comprises:

input means for entering a password at the log-in;

identification means for identifying an operator based on the passwordthat is input; and

control means for, when the operator is a common user who is permittedto log in, permitting the user to log in and displaying a menu screenfor a common user, and for, when the operator is a manager, permittingthe manager to log in and displaying a menu screen for the manager.

According also to one further aspect of the present invention, aninformation processing apparatus comprises:

identification means for ascertaining whether an operator is a manager;

permission means for permitting the operator to instruct the deletion ofall printing instructions stored in a print queue; and

deletion means for, upon receipt of the instruction, deleting all of theprinting instructions in the print queue.

According also to yet one more aspect of the present invention, aninformation processing apparatus comprises:

identification means for ascertaining whether an operator is a manager;

permission means for permitting the operator to setup a general timelimit for a process instruction; and

management means for managing the process instruction based on thesetup.

According also to yet another aspect of the present invention, aninformation processing apparatus comprises:

proxy device setup means for setting up as a proxy device a differentdevice having a voice modem; and

communication control means for performing voice communication bytelephone using the device that is set up by the proxy device setupmeans.

According also to yet an additional aspect of the present invention, aninformation processing method comprises:

an input step of entering a password at the log-in;

an identification step of identifying an operator based on the passwordthat is input; and

a control step of, when the operator is a common user who is permittedto log in, permitting the user to log in and displaying a menu screenfor a common user, and of, when the operator is a manager, permittingthe manager to log in and displaying a menu screen for the manager.

According also to yet a further aspect of the present invention, aninformation processing method comprises:

an identification step of ascertaining whether an operator is a manager;

a permission step of permitting the operator to instruct the deletion ofall printing instructions stored in a print queue; and

a deletion step of, upon receipt of the instruction, deleting all of theprinting instructions in the print queue.

According also to yet one further aspect of the present invention, aninformation processing method comprises:

an identification step of ascertaining whether an operator is a manager;

a permission step of permitting the operator to setup a general timelimit for a process instruction; and

a management step of managing the process instruction based on thesetup.

According to one more aspect of the present invention, an informationprocessing method comprises:

a proxy device setup step of setting up as a proxy device a differentdevice having a voice modem; and

a communication control step of performing voice communication bytelephone using the device that is set up at the proxy device setupstep.

According to another aspect of the present invention, provided is astorage medium on which is stored a program, which comprises:

an input step of entering a password at the log-in;

an identification step of identifying an operator based on the passwordthat is input; and

a control step of, when the operator is a common user who is permittedto log in, permitting the user to log in and displaying a menu screenfor a common user, and of, when the operator is a manager, permittingthe manager to log in and displaying a menu screen for the manager.

According to an additional aspect of the present invention, provided isa storage medium on which is stored a program, which comprises:

an identification step of ascertaining whether an operator is a manager;

a permission step of permitting the operator to instruct the deletion ofall printing instructions stored in a print queue; and

a deletion step of, upon receipt of the instruction, deleting all of theprinting instructions in the print queue.

According to a further aspect of the present invention, provided is astorage medium on which is stored a program, which comprises:

an identification step of ascertaining whether an operator is a manager;

a permission step of permitting the operator to setup a general timelimit for a process instruction; and

a management step of managing the process instruction based on thesetup.

According to one further aspect of the present invention, provided is astorage medium on which is stored a program, which comprises:

a proxy device setup step of setting up as a proxy device a differentdevice having a voice modem; and

a communication control step of performing voice communication bytelephone using the device that is set up at the proxy device setupstep.

According to yet one more aspect of the present invention, aninformation processing apparatus comprises:

object information storage means for storing object information to beprocessed;

object information list display means for displaying as a list objectinformation stored in the object information storage means;

object information selection means for selecting object information thatis to be published;

setup means for setting a publication time limit; and

published information registration means for registering as publishedinformation, in conjunction with the publication time limit that is setby the setup means, the object information in the published informationstorage means that is selected by the selection means.

According to yet another aspect of the present invention, an informationprocessing method comprises:

an object information list display step of displaying as a list objectinformation stored in an object information storage unit for storing theobject information to be processed;

an object information selection step of selecting object informationthat is to be published;

a setup step of setting a publication time limit; and

a published information registration step of registering as publishedinformation, in conjunction with the publication time limit that is setat the setup step, the object information in the published informationstorage unit that is selected at the selection step.

According to yet an additional aspect of the present invention, providedis a storage medium on which is stored a program, which comprises:

an object information list display step of displaying as a list objectinformation stored in an object information storage unit for storing theobject information to be processed;

an object information selection step of selecting object informationthat is to be published;

a setup step of setting a publication time limit; and

a published information registration step of registering as publishedinformation, in conjunction with the publication time limit that is setat the setup step, the object information in the published informationstorage unit that is selected at the selection step.

According to yet a further aspect of the present invention, aninformation processing apparatus comprises:

published information storage means for storing information to bepublished in conjunction with a publication time limit;

determination means for determining whether the publication time limithas expired for the information stored in the published informationstorage means;

publication list display means for displaying as a list information forwhich the determination means has determined that the publication timelimit has not yet expired;

information selection means for selecting information from the listdisplayed by the publication list display means; and

output means for outputting the contents of information that is selectedby the selection means.

According to yet one further aspect of the present invention, aninformation processing method comprises:

a determination step of determining whether the publication time limithas expired for information stored in a published information storageunit for storing the information to be published in conjunction with apublication time limit;

a publication list display step of displaying as a list information forwhich it has been determined at the determination step that thepublication time limit has not yet expired;

an information selection step of selecting information from the listdisplayed at the publication list display step; and

an output step of outputting the contents of information that isselected at the information selection step.

According to still one more aspect of the present invention, provided isa storage medium on which is stored a program, which comprises:

a determination step of determining whether the publication time limithas expired for information stored in a published information storageunit for storing the information to be published in conjunction with apublication time limit;

a publication list display step of displaying as a list information forwhich it has been determined at the determination step that thepublication time limit has not yet expired;

an information selection step of selecting information from the listdisplayed at the publication list display step; and

an output step of outputting the contents of information that isselected at the information selection step.

Other objectives and advantages besides those discussed above shall beapparent to those skilled in the art from the description of a preferredembodiment of the invention which follows. In the description, referenceis made to accompanying drawings, which form a part thereof, and whichillustrate an example of the invention. Such example, however, is notexhaustive of the various embodiments of the invention, and thereforereference is made to the claims which follow the description fordetermining the scope of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating the functional arrangement of oneembodiment of the present invention;

FIG. 2 is a detailed diagram illustrating the functional arrangement ofthe embodiment;

FIG. 3 is a diagram showing the transmission of information inaccordance with the manipulation of input devices performed by a user;

FIG. 4 is a detailed diagram showing the sequence of the processingperformed until a command entered by a user is executed;

FIG. 5 is a diagram showing the sequence of the processing performed todisplay for a user the processing results and a status change;

FIG. 6 is a diagram illustrating the functional relationship existingamong a plurality of devices;

FIG. 7 is a diagram illustrating a system configuration according to theembodiment;

FIG. 8 is a diagram illustrating the essential hardware arrangementaccording to the embodiment;

FIG. 9 is a flowchart showing the order of activation when power isswitched on;

FIG. 10 is a flowchart showing the processing performed by a clientcomponent;

FIG. 11 is a flowchart showing the processing performed by a servercomponent upon receiving a request from a client;

FIG. 12 is a flowchart showing the CancelAllPrinterjobs processing;

FIG. 13 is a flowchart showing the GetAllPrinterjobs processing;

FIG. 14 is a flowchart showing the SetPrinterJobStatus processing;

FIG. 15 is a flowchart showing the processing performed for requests“Login” and “Logout”;

FIG. 16 is a flowchart showing. the processing performed for requests“GotoOtherDevice” and “GotoDesktop”;

FIG. 17 is a flowchart showing the processing performed for requests“Search”, “Help” and “Receive Job/Receive Notification”;

FIG. 18 is a flowchart showing the IdAnalyze processing;

FIG. 19 is a flowchart showing the DUMMY processing;

FIG. 20 is a flowchart showing the IdAnalyzeNotify processing;

FIG. 21 is a flowchart showing the ReceiveHttpNotification processing;

FIG. 22 is a flowchart showing the processing performed for requests“Print”, “Send”, “Delete”, “Reschedule”, and “Preview”;

FIG. 23 is a flowchart showing the PrintJob processing;

FIG. 24 is a flowchart showing the SendJob processing;

FIG. 25 is a flowchart showing the SendJob transmission processing;

FIG. 26 is a flowchart showing the CancelJob processing;

FIG. 27 is a flowchart showing the SendNotification processing;

FIG. 28 is a diagram showing the relationship between input informationfor a server and corresponding processes;

FIG. 29 is a flowchart showing the processing performed beginning withthe activation of a daemon;

FIG. 30 is a flowchart showing the notification processing performed bya daemon module;

FIG. 31 is a diagram showing the relationship between the job types thatare handled by the daemon and corresponding processes;

FIG. 32 is a flowchart showing the PrintPrinterJob processing;

FIG. 33 is a flowchart showing the SendJob processing;

FIG. 34 is a flowchart showing the ReceiveJobData processing;

FIG. 35 is a flowchart showing the GetListOfJobAttributes processing;,

FIG. 36 is a flowchart showing the PollJob processing;

FIG. 37 is a flowchart showing the PollNotify processing;

FIG. 38 is a flowchart showing the CancelAction processing;

FIG. 39 is a flowchart showing the EditAction processing;

FIG. 40 is a flowchart showing the EditAction processing;

FIG. 41 is a flowchart showing the RescheduleAction processing;

FIG. 42 is a flowchart showing the RescheduleAction processing;

FIG. 43 is a flowchart showing the RescheduleAction processing;

FIG. 44 is a flowchart showing the AddNotification processing;

FIG. 45 is a flowchart showing the AddInstruction processing;

FIG. 46 is a flowchart showing the GetInstruction processing;

FIG. 47 is a flowchart showing the ExecutionInstruction processing;

FIG. 48 is a flowchart showing the processing performed by a desktopserver component;

FIG. 49 is a flowchart showing the processing performed for a requestconcerning mail;

FIG. 50 is a flowchart showing the processing performed for a requestconcerning a schedule;

FIG. 51 is a flowchart showing the processing performed for a requestconcerning another device;

FIG. 52 is a flowchart showing the processing performed for a requestconcerning logout and help;

FIG. 53 is a flowchart showing the processing performed on an initialmenu screen;

FIG. 54 is a flowchart showing the processing performed for publicinformation;

FIG. 55 is a flowchart showing the login processing;

FIG. 56 is a flowchart showing the processing performed to select a joband to perform an action;

FIG. 57 is a flowchart showing the processing performed to preview aselected Job;

FIG. 58 is a flowchart showing the processing performed to delete aselected Job;

FIG. 59 is a flowchart showing the processing performed to change aschedule for a selected Job;

FIG. 60 is a flowchart showing the processing performed to print aselected Job;

FIG. 61 is a flowchart showing the processing performed to change aprint setup for a selected Job;

FIG. 62 is a flowchart showing the processing performed to transmit aselected Job;

FIG. 63 is a flowchart showing the processing performed to change atransmission setup for a selected Job;

FIG. 64 is a flowchart showing the processing performed beginning at amain menu;

FIG. 65 is a flowchart showing the search processing;

FIG. 66 is a flowchart showing the processing performed to addinformation to public information;

FIG. 67 is a flowchart showing the printing processing;

FIG. 68 is a flowchart showing the remote printing processing performedby a printer;

FIG. 69 is a flowchart showing the transmission processing;

FIG. 70 is a diagram showing an example transmission setup menu;

FIG. 71 is a diagram showing an example transmission setup change menu;

FIG. 72 is a flowchart showing the remote sending processing performedby a printer;

FIG. 73 is a diagram showing an example menu for selecting a devicewherein a Job to be deleted is located;

FIG. 74 is a diagram illustrating an example list for Jobs to bedeleted;

FIG. 75 is a flowchart showing the deletion processing;

FIG. 76 is a flowchart showing the remote deletion processing performedby a printer;

FIG. 77 is a flowchart showing the command setup processing;

FIG. 78 is a flowchart showing the schedule change processing;

FIG. 79 is a flowchart showing the remote rescheduling processing;

FIG. 80 is a flowchart showing the processing performed to accessanother device;

FIG. 81 is a diagram showing a setup screen for accessing anotherdevice;

FIG. 82 is a flowchart showing the desktop processing;

FIG. 83 is a flowchart showing the processing performed for unread mail;

FIG. 84 is a flowchart showing the processing performed for read mail;

FIG. 85 is a diagram showing an example unread mail list;

FIG. 86 is a diagram showing an example display for the content of mail;

FIG. 87 is a diagram showing an example read mail list;

FIG. 88 is a flowchart showing the file processing;

FIG. 89 is a flowchart showing the ResetInstructions processing;

FIG. 90 is a flowchart showing the DeleteAllInstructions processing;

FIG. 91 is a flowchart showing the DeleteInstructions processing;

FIG. 92 is a flowchart showing the GetInstructionDetails processing;

FIG. 93 is a flowchart showing the Check processing;

FIG. 94 is a flowchart showing. the GetJobData processing;

FIG. 95 is a flowchart showing the GetJobAttributes processing;

FIG. 96 is a flowchart showing the GetActionAttributes processing;

FIG. 97 is a flowchart showing the DeleteJob processing;

FIG. 98 is a flowchart showing the GetNotificationList processing;

FIG. 99 is a flowchart showing the SetNotificationCondition processing;

FIG. 100 is a flowchart showing the SetNotificationCondition processing;

FIG. 101 is a flowchart showing the SetNotificationStatus processing;

FIG. 102 is a flowchart showing the ClearHistory processing;

FIG. 103 is a flowchart showing the DeleteAllPublicInfoJobs processing;

FIG. 104 is a flowchart showing the PrintPublicInfo processing;

FIG. 105 is a flowchart showing the SearchData processing;

FIG. 106 is a diagram showing an example screen for an initial menu;

FIG. 107 is a diagram showing a URL print setup screen;

FIG. 108 is a diagram showing a password input screen;

FIG. 109 is a diagram showing a setup screen for the processingperformed for a job selected from a print queue;

FIG. 110 is a diagram showing a setup screen for processing publicinformation;

FIG. 111 is a diagram showing an example setup screen for publishinginformation using another device;

FIG. 112 is a diagram showing a login screen;

FIG. 113 is a diagram showing an example pending job list;

FIG. 114 is a diagram showing a job preview screen example;

FIG. 115 is a diagram showing a screen for confirmation of deletion;

FIG. 116 is a diagram showing a setup screen for changing a schedule;

FIG. 117 is a diagram showing an example print setup menu;

FIG. 118 is a diagram showing a notification setup screen;

FIG. 119 is a diagram showing an example print setup change menu;

FIG. 120 is a diagram showing an example correction menu;

FIG. 121 is a diagram showing an example main menu;

FIG. 122 is a diagram showing an example menu for designating a positionwhereat a job to be printed is located;

FIG. 123 is a diagram showing an example menu for selecting a job to beprinted;

FIG. 124 is a diagram showing an example menu for designating a positionwhereat a job to be transmitted is located;

FIG. 125 is a diagram showing an example menu for selecting a job to betransmitted;

FIG. 126 is a diagram showing an example command setup screen;

FIG. 127 is a diagram showing an example menu for designating a devicewhereat a Job to be changed is located;

FIG. 128 is a diagram showing an example screen for selecting a Job forwhich a schedule is to be changed;

FIG. 129 is a diagram showing an example desktop main menu;

FIG. 130 is a diagram showing an example setup screen for obtaining afile;

FIG. 131 is a diagram showing an example desktop file list;

FIG. 132 is a diagram showing an example screen for selecting theprocessing to be performed for an obtained file;

FIG. 133 is a diagram showing a setup screen for establishinglimitations for a job;

FIG. 134 is a diagram showing a setup screen for setting a rejection fora job;

FIG. 135 is a diagram for explaining the structure of a job;

FIG. 136 is a diagram showing the functional arrangement of theembodiment;

FIG. 137 is a flowchart showing the Logout screen creation processing;

FIG. 138 is a flowchart showing the Logout screen processing;

FIG. 139 is a diagram showing the Logout screen;

FIG. 140 is a diagram showing the logout screen;

FIG. 141 is a flowchart showing the call response processing;

FIGS. 142A and 142B are flowcharts showing the main screen processingfor a manager;

FIG. 143 is a diagram showing an example manager main screen;

FIG. 144 is a flowchart showing the network setup screen processing;

FIG. 145 is a diagram showing an example network setup screen;

FIG. 146 is a flowchart showing the job setup screen processing;

FIG. 147 is a diagram showing an example job setup screen;

FIG. 148 is a flowchart showing the resource setup screen processing;

FIG. 149 is a diagram showing an example resource setup screen;

FIG. 150 is a flowchart showing the modem proxy setup screen processing;

FIG. 151 is a diagram showing an example modem proxy setup screen;

FIG. 152 is a flowchart showing the other setup screen processing;

FIG. 153 is a diagram showing an example other setup screen;

FIG. 154 is a flowchart showing the password setup screen processing;

FIG. 155 is a diagram showing an example password setup screen;

FIG. 156 is a flowchart showing the public information deletion screenprocessing;

FIG. 157 is a diagram showing an example public information deletionscreen;

FIG. 158 is a flowchart showing the job database management screenprocessing;

FIG. 159 is a diagram showing an example database management screen;

FIG. 160 is a flowchart showing the shutdown screen processing; and

FIG. 161 is a diagram showing an example shutdown screen.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The preferred embodiment of the present invention will now be describedin detail while referring to the accompanying drawings.

FIG. 1 is a diagram showing the functional arrangement of theembodiment. A client component 102 and a server 103 may be present inthe same device, or may be in different devices connected across anetwork, etc.

When a user 101 specifically operates the client component 102, theclient component 102 transmits to the server 103 a request thatcorresponds to the operation. The server 103 interprets the receivedrequest, and adds or deletes a job to or from a database 104, oracquires data from the database 104. As a result, a response is preparedin HTML (Hyper Text Markup Language), as needed, and is transmitted tothe client component 102. The client component 102 displays the receivedHTML data and allows the user 101 to perform additional devicemanipulations.

A daemon module 105 monitors the job stored in the database 104, andperforms the processing (printing, transmission or notification) thatcorresponds to the job for which the execution condition is satisfied.

FIG. 2 is a detailed diagram showing the functional arrangement of theembodiment.

The client component 102 is constituted by an operating unit 201 and twoWeb browsers 202 and 203. The user manipulates the operating unit 201,and an instruction for starting the processing is converted into arequest by the Web browser 202, while an instruction for displaying thestatus of a device (printer 206) is converted into a request by the Webbrowser 203. These requests are transmitted to the server component 103.

The server component 103 is constituted by a Web server 204, a devicemanager 205, a request manager 207, and a command analysis/process unit208. A request originating at the client component 102 is received bythe Web server 204, which in turn transmits the request to the devicemanager 205 or to the request manager 207.

In accordance with the request, the device manager 205 either acquiresthe status of the printer 206 or exercises control of the printer 206.The request manager 207 converts the request into a process command, andtransmits it to the command analysis/process unit 208.

The command analysis/process unit 208 performs the processingcorresponding to the process command, and accesses the database 104 viaa database manager 209 to add or to update a job.

The daemon module 105 accesses the database 104 via the database manager209 at a constant time interval, and determines whether there is a jobfor which the execution condition is satisfied. If there is such a job,the daemon module 105 executes a corresponding process.

FIG. 3 is a diagram showing the transmission of information inaccordance with the operations performed by a user.

The client component 102 receives as input information the data producedby the operations performed by the user, and generates a request andtransmits it to the server component 103.

The server component 103 interprets the received request, andcommunicates with the database 104 via the database manager 209 to addor to update a job, or to acquire data. In addition, the servercomponent 103 communicates with the printer 206 to obtain the status ofthe printer 209. As a result, the server component 103 generates, asneeded, a corresponding display command (an HTML page) and transmits itto the client component 102.

The client component 102 displays the received display command (an HTMLpage) for the user, and allows the user to perform a new operation.

Jobs stored in the database 104 are monitored by the daemon module 105via the database manager 209, and a job for which the executioncondition is satisfied is printed or transmitted, or brought to theattention of the user.

FIG. 4 is a detailed diagram showing the sequence of the processingperformed until a command corresponding to the user's entry is executed.

The manipulation of data input devices by the user is converted intocorresponding operation instruction data by the operating unit 201. Forexample, the manipulation by the user of a keyboard or of a mouse isconverted into corresponding key code or into information, such as mousemovement information, that can be handled by an information processingapparatus.

The operating instruction data converted by the operating unit 201 areconverted into a corresponding request by the Web browser 202, and therequest is transmitted to the Web server 204. When, for example, one ofthe buttons on a screen is selected, a request “selection of a specificbutton” is prepared.

The Web server 204 transmits the received request to the request manager207, which thereafter converts the request into a corresponding processcommand and transmits it to the command analysis/process unit 208. When,for example, the user chooses a button to instruct printing, a request“selection of a print button” is converted into a print command“execution of a process corresponding to the print button”, and printingis performed.

FIG. 5 is a diagram showing the sequence of the processing performeduntil the results of the processing and the change in the status of theprinter 206 are displayed for a user.

The request manager 207 receives the process result from the commandanalysis/process unit 208, and transmits corresponding operatinginstruction data to the Web server 204. Similarly, the device manager205 detects the change of the status of the printer 206 and transmitscorresponding operating instruction data to the Web server 204. Todisplay, for example, a new operating screen as the processing result,the contents to be displayed are converted into HTML data for the newoperating screen. Also, to display a new screen for the status of theprinter 206, the contents to be displayed are converted into HTML datafor the screen.

The Web server 204 transmits the received operating screen data to theWeb browsers 202 and 203. The Web browser 202 provides the data for auser by displaying the data on a display operating unit, such as a touchpanel. The Web browser 203 displays the status of the printer 206.

FIG. 6 is a diagram showing the functional relationship among aplurality of devices (device A and device B in this embodiment). In thisembodiment, device A is a printer, and device B is a desktop personalcomputer for managing both a user's mail and a schedule. The devices Aand B each include a client component 102, a server component 103 and adaemon module 105. It should be noted, however, that the user is locatedon the same side as is the device A, and the client component 102 of thedevice B is not shown.

When the user manipulates the device A, the operating unit 201 acquiresas input information the information input by the user's manipulation ofthe device, and transmits it as a request to the device manager 205 andthe request manager 207 in the server component 103.

The device manager 205 responds to the user's request by acquiring thestatus of the printer 206. In accordance with the type of the request,the request manager 207 permits a printer control unit 601 to controlthe printer 206, or permits the command analysis/process unit 208 toanalyze more detailed information and to perform a correspondingprocess.

As a result, the information form is changed by a conversion controlunit 603, as needed, or various processes are performed by a controller602. When it is determined that management of the job is required, theaddition of a job or the updating of a job is performed for the database104. When it is determined that the display of data is required, thedata are displayed by a display control unit 604. When it is determinedthat the issuance of a data notification is required, the datanotification is issued by a notification control unit 605.

The daemon module 105 periodically monitors the database 104. When thereis a job for which the execution condition is satisfied, the daemonmodule 105 executes the corresponding processing.

When it is determined that the processing has not been completed by thedevice A, a request is issued to the device B, and the request manager207 of the device B performs the corresponding process. To print a fileat the device B, for example, a printing unit 607 employs acorresponding application, and for accessing mail, a mail control unit608 employs a corresponding application. For other operations, suchreferencing schedule information, a corresponding application isemployed.

In addition, a job stored in the database 104 of the device B can alsobe accessed.

FIG. 7 is a diagram showing the configuration of a system according tothis embodiment.

In FIG. 7, various apparatuses are connected to a network 701, and dataare exchanged across the network 701. A printer 702, which includes aninput/output operation unit 703, prints data received across the network701. The input/output operating unit 703 provides various displays for auser, and accepts instructions from the user. A scanner 704 and amulti-function apparatus 705 also include such an input/output operatingunit. The scanner 704 optically reads data printed on paper, etc., andthe multi-function apparatus 705 functions as the printer 702 and as thescanner 704. A personal computer 706 creates documents and images, andmanages for the user such personal data as mail and a schedule.

FIG. 136 is a diagram showing the functional arrangement for theembodiment.

Features of this arrangement are that a process instruction command(job) is employed as one process unit, and that a job generation unit1362, an analysis/performance unit 1363 and an output unit 1364 areoperated at adequate timings.

A detailed explanation will now be given for a job. FIG. 135 is adiagram for explaining the structure of a job.

A job includes a process (Action), a process performance condition(Condition), a process performance instructor=owner (Owner), a currentprocess status (Status), and information concerning a process creationtime (Created Time) and the job that triggered the creation (ParentJob). With the job, the previously performed process can be refereed toand the performance of a new process can be instructed.

The above process performance conditions (Condition) are When To Do(initiation when a designated time has been reached), After Time(initiation after a designated time has elapsed), Before Time(initiation before a designated time has elapsed), On Action (initiationupon the performance of a designated process), Object (initiation at thetime for a designated object), From (initiation at the time for adesignated process source), By (initiation when a designated method isemployed for a process), Device Status (initiation when the status of adevice attains a designated value), and Result Status (initiation inaccordance with the process results obtained).

The values for the Device Status are OK, Toner low, Staples low,Unknown, Printing, No toner cart, Printer open, Paper jam, Hardwarefailure, Tray failure, Paper deck open, and Stapler low.

The values for the Result Status are Success, Fail, and Hold jobaccessed.

The Owner represents the issuer of process execution instructions, i.e.,the owner of the processes, and includes User Device ID, User ID,Password, and User Type. The types of users are Sender, Receiver, Other,Receiver to be, and Don't care.

The values for the process status (Status) are Done (executionterminated), To Do (execution scheduled), Don't care (invalid), Cancel(deleted), Active (in progress), Spooling (spooling in progress), Failed(execution failure) and Ignored (execution ignored).

The Action includes the types of processes that were performed or are tobe performed (Type), the object to be processed (Object), Object Count(the number of copies of the object), To (process destination), From(process source), By (process method), and all other process associatedinformation.

The types of processes (Type) are None, Get, Send, Delete, Scan, Extractdata, Print, File, Set instruction, Hold, Extend hold, Pause printing,Change priority, Receive, Convert, Notify, and Operate.

As the Object, there are Action and Object. To (process destination) andFrom (process source) include the Sender or the Receiver, as a Person,and a Device. By (process method) includes Popup window, Voice message,E-mail, Fax, Phone, and Pager.

The Object includes the substance of an object (Content), managementinformation such as the data format (Format) and the size (Size) of theobject, additional information (Addition) concerning the object, such asa comment, and source information (Source) for the object. For a filehaving a print format, the original MS-Word file is employed as sourceinformation.

The data formats (Format) of the object are Text, Html, Rtf, Bmp, Tiff,Pcx, Jpeg, G3, G4, Pc15, and MS-Word.

Referring again to FIG. 136, the job generation unit 1362, theanalysis/performance unit 1363 and the output unit 1364 are installed ina control box 1361, which is connected to a conventional printer 206.The printer 206, as in the prior art, receives external printinformation, performs the printing process in accordance with aninstruction, and outputs the print results.

First, an explanation will be given for the time that an instruction isentered by a user. When the user enters a specified instruction via anoperating unit 101, the job generation unit 1362 generates a jobcorresponding to the instruction, and adds the job to the database 104.

The job added to the database 104 is monitored by theanalysis/performance unit 1363, and whether the execution condition hasbeen satisfied is sequentially examined. If there is a job for which theexecution condition has been satisfied, a corresponding process isperformed, and the database 104 is updated using the job that reflectsthe execution result.

When, for example, the user instructs the printing of specific data at adesignated time, the job generation unit 1362 generates as a job thecontents of the operation input by the user, and adds the job to thedatabase 104.

At this time, if the database 104 includes a job “analyze the contentsof an operation entered by a user and re-register this job”, whichdesignates a process to be performed when the operation input by theuser takes place, the analysis/performance unit 1363 for detecting thepresence of an unanalyzed job in the database 104 analyzes the contentsof the operation entered by the user, determines a corresponding processto be performed and generates it as a job, and adds the job to thedatabase 104.

In this case, the printing process is added as a job to the database104. Also, the job that represents the contents of the operation inputby the user is regarded as having already been analyzed and updated, andthe above mentioned job for analyzing the user's operation isre-registered.

When the time designated by the user is reached, the job for theprinting process is performed, and print information 107 is generatedand transmitted to the printer 206. When new job print results areobtained, the job “reflect the print results in this job” is added tothe database 104. The printer 206, as in the prior art, performs theinstructed, and outputs the print results. In addition, after theprinting has been completed, the print results are obtained as theprinter status from the printer 206, and are reflected in the job.

When in this embodiment the paper or the toner has run out, or an errorhas occurred at the printer 206, job generation unit 1362 obtains thechange in the printer status for the printer 206, and generates acorresponding job and adds it to the database 104. When it isascertained from the printer status for the printer 206 that the tonerhas run out, the occurrence of the change in the printer status iscreated as a job and is added to the database 104.

At this time, if the database 104 includes the job “issue an orderrequest when toner has run out, and re-register this job”, whichdesignates a process to be performed upon the occurrence of a change inthe status, an order request is issued and the job is re-registered. Asa result, each time a like condition occurs, this process is performed.

The process performed for the change in the status of the printer 206 isalso performed for changes in the internal statuses of the othersections.

As an example, there is one case where the backlight for a liquidcrystal display panel 801, which will be described later, is poweredoff. When the database 104 includes the job “perform initializationprocess when the backlight is powered off, and reregister this job”,which designates a process to be performed upon the occurrence of thechange in the status, the initialization process is performed and thejob is re-registered. As a result, the periodical initialization processthat is required for stably activating a product can be performed inconsonance with a timing that is satisfactory under the circumstances.

When the job generation unit 1362 is notified of a change in theexternal status, it generates a corresponding job and adds it to thedatabase 104.

When, for example, an error has occurred in an external printerconnected across a network, the occurrence of the change in the externalstatus is generated as a job and is added to the database 104. At thistime, if the database 104 includes the job “transmit a job transmissioninstruction when an error has occurred in an external printer, andre-register this job”, which designates a process to be performed uponthe occurrence of a change in the external status, a job transmissioninstruction is transmitted by the output unit 1364 to the printer atwhich the error occurred, and this job is re-registered in the database104. As a result, each time a like condition occurs, the same process isperformed.

When a process instruction (job) is received from an external device,the job generation unit 1362 generates a corresponding job and adds itto the database 104.

For example, upon receiving a job transmission instruction, thereception of the job transmission instruction is generated as a job andis added to the database 104.

At this time, if the database 104 includes the job “add a received joband re-register it”, which designates a process to be performed uponreceiving the job, the job transmission instruction is added and the jobis re-registered.

Sequentially, when the execution condition of the job transmissioninstruction is matched, a transmission process corresponding to the jobis performed and the job is transmitted.

Next, an explanation will be given for a case wherein a job transmissioninstruction other than the above, i.e., a print information transmissioninstruction, is received.

To print information stored in another information output apparatus, thecorresponding print information must be extracted from the above printinformation. Transmission of the print information by the pertinentapparatus is one method that is employed. With this method, however, aprinting function for the information is required by an informationrequesting apparatus. In this embodiment, an explanation will be givenfor another method for the transmission of print information thatcorresponds to the information stored in a specific apparatus.

When a print information transmission instruction 106 is received from aspecific device, the receipt of the job is generated as a job and addedto the database 104. Then, when the execution condition of the job ismatched, a print information transmission process that corresponds tothe job is performed. In the print information transmission process,print information is prepared from the requested information and istransmitted as instructed.

In the information output apparatus that has received the printinformation, the job generation unit 1362 generates as a job theacquisition of print information, and adds it to the database 104.

At this time, as is described above, since when the print informationtransmission instruction was issued the job “execute a printing processupon receiving from a transmission source print information for a printinformation transmission instruction” was added to the database 104,with the assumption that print information had been received, theprinting process is performed, and the received print information istransmitted to the printer 206, which then initiates the printing andoutputs the printing results.

In addition to the above described process instruction, there areinstructions for notification and for output. These process instructionsmay be externally received or may be stored in the database 104 inadvance.

For example, when the execution condition of the notificationinstruction is matched, the notification process is performed usingE-mail, a telephone, or a facsimile machine. When the executioncondition of the output instruction is matched, the output process isperformed, and a display is provided or a voice is released.

FIG. 8 is a diagram showing the essential hardware arrangement accordingto the embodiment. Switches, a fan, etc., are not shown.

An information output apparatus according to the embodiment of thepresent invention includes input devices, such as a microphone 809, atouch panel 801, a keyboard/mouse 810, an IrDA transmission/receptionunit 811, a network 804 and a modem 812, and acquires informationthrough an input unit 803.

The touch panel 801 is used to display for the user the printer statusand a menu screen. And when the user touches the display screen, a menuitem can be selected and characters can be entered using a keyboard thatis displayed. A common display and a common keyboard may be used insteadof the touch panel 801.

The status of the printer 206 is also obtained via a centrocable fromthe input unit 803. Besides the status of the printer 206, the internalstatus is detected and obtained by an internal sensor or a monitor.

The processing results are output by an output unit 813 to certainoutput devices, such as the printer 206, a display 814, a loudspeaker815, an LED 816, the IRDA transmission/reception unit 811, the network804, and the modem 812. When the printing process is performed, forexample, the print information is transmitted via the centrocable to theprinter 206. The printer 206 performs the printing in accordance withthe received print information, and outputs the printing results. Itshould be noted that the input unit 803 and the output unit 813 are notnecessarily physically separate components.

A CPU 802 executes various programs, including the processing which willbe described later while referring to the flowcharts, and controls theindividual sections connected by a system bus 808. Further, by executingcorresponding programs, the CPU 802 provides the functions for the jobgeneration unit 1362, the analysis/performance unit 1363, and the outputunit 1364 that are described above.

A ROM 805 is used to store fixed data and programs. A RAM 806 is used totemporarily store data and programs. A hard disk drive (HDD) 807 is usedfor the above described database 104 as permanent storage for programsand data. The system bus 808 is employed as a medium for the connectionof the above individual sections and for the exchange of data, addresssignals and control signals by the sections.

The programs, including the processing which will be described laterwhile referring to the flowcharts, may be stored in the ROM 805, or maybe loaded from the HDD 807 into the RAM 806, as needed, before theinitiation of the processing or during the performance of theprocessing. An external storage device, such as an MO drive, may beemployed instead of the HDD 807.

With the above described arrangement, the job generation unit 1362generates a job that corresponds to the input information and adds it tothe database 104 on the hard disk 807; the analysis/performance unit1363 obtains a job from the database 104 and performs a correspondingprocess; and the output unit 1364 outputs the processing results.

FIG. 9 is a flowchart showing an activation order when a user powers ona machine. When at step S901 the user turns on the power, at step S902the OS is activated, and at step S903 the Web server 103 is activated.Then, at step S904 the client component 102 is activated, and finally atstep S905 the daemon module 105 is activated.

FIG. 10 is a flowchart showing the processing performed by the clientcomponent 102.

When the client component 102 is activated, at step S1001 a Web browserobject is created, and at step S1002, a request to prepare an HTML pageis issued to the server component 103. The page at this time is anopening screen. At step S1003 the HTML page transmitted by the server103 as a response is displayed, and at step S1004 input by the user iswaited for. Then, a process corresponding to the user's input isperformed. When at step S1005 a request from the user is “exit”, at stepS1006 the system is shut down, and the processing is thereafterterminated. When at step S1007 the request from the user should beprocessed by the client component 102, at step S1009 this process ishandled and input by the user is again waited for. When the processshould be performed by the server 103, at step S1008 a process requestis issued to the server component 103, and an HTML page prepared as aconsequence of the request is received and displayed. Then, input by theuser is again waited for.

FIG. 11 is a flowchart showing the processing performed by the servercomponent 103 upon receiving a request from the client component 102.

The server component 103 receives a request from the client component102 at step S1101, and analyzes this request at steps S1102 to S1103 andperforms a corresponding process. As for a request for the display of anOpeningScreen page, at step S1104 the printer status is obtained. As fora Cancel All Jobs request, at step S1105 the CancelAllPrinterJobs( )function, which will be described later while referring to FIG. 12, iscalled, and all the jobs are canceled. As for the Cancel/Pause/Restartrequest, at step S1106 the SetPrinterJobsStatus( ) function is called,and a designated status is set for the job.

For all these requests, at step S1107 a corresponding HTML page isfinally prepared, and at step S1108 the HTML page is transmitted to theclient component 102. The processing is thereafter terminated.

The processing performed for the request “login” or “logout” will bedescribed later while referring to FIG. 15, and the processing performedfor the request “GotoOtherDevice” or “GotoDesktop” will be describedlater while referring to FIG. 16. Further, the processing performed forthe request “Search”, “Help” or “Receive Job/Receive Notification” willbe described later while referring to FIG. 17, and the processingperformed for the request “Print”, “Send”, “Delete”, “Reschedule” or“Preview” will be described later while referring to FIG. 22.

FIG. 12 is a flowchart showing the CancelAllPrinterjobs processing. Theprototype is DWORD CancelAllPrinterjobs( ).

First, at step S1201 the GetAllPrinterJobs function, which will bedescribed later while referring to FIG. 13, is called, and jobs areobtained from the spool. At step S1202 a specific printer is opened, andat step S1203 the statuses of the individual jobs that are to becanceled are set to “Cancel”. Then, at step S1204 the printer is closed.This process is repeated until the statuses of all the jobs have beenset to “Cancel”.

FIG. 13 is a flowchart showing the GetAllPrinterjobs processing. Theprototype is Int GetAllPrinterjobs(pInfo).

First, at step S1301 the EnumPrintero function is employed to list aprinter, a print server, a domain and a print provider that areavailable. At step S1302 one of the listed objects is opened, and atstep S1303 a job available in the spool is listed by using the EnumJob() function. At step S1304 the printer is closed. This process isperformed for all the objects.

FIG. 14 is a flowchart showing the SetPrinterJobStatus processing. Theprototype is Int SetPrinterJobStatus(pPrinterName, JobId, Status).

First, at step S1401 the GetJob function is employed to extract adesignated job from the spool. At step S1402 a specific printer whereatthe job is present is opened, and at step S1403 the status of the job isset to a designated value. At step S1404 the printer is closed, and theprocessing is thereafter terminated.

FIG. 15 is a flowchart showing the processing performed by the server103 when the request from the client component 102 is “Login” or“Logout”.

When at step S1501 the request is “Login”, first, at step S1502 a loginverb and a remote device list are obtained, and at step S1503 the nameof a user is acquired. At step S1504 the GetUserId( ) function is calledto obtain a job list for the user. At step S1505 a corresponding HTMLpage is prepared, and at step S1506 detailed information for the userand the job are stored in a hidden domain on the HTML page.

When the request from the client component 102 is “Logout”, at stepS1507 a check is performed to determine whether the remote device listis empty. When the list is empty, at step S1510 the OpeningScreen pageis created in accordance with the existing status. When the remotedevice list is not empty, at step S1508 the next device is logged-inusing the login verb “Disconnect”, and at step S1509 the device isdeleted from the remote device list. The processes at steps S1508 andS1509 are repeated until the list is emptied. That is, until all thedevices in the remote device list are logged out. When the list has beenemptied, the OpeningScreen page is prepared.

For both of the requests “Login” and “Logout”, at step S1511 theobtained page is finally transmitted to the client component 102, andthe processing is thereafter terminated.

FIG. 16 is a flowchart performed by the server when the request from theclient component 102 is “GotoOtherDevice” or “GotoDesktop”.

When at step S1601 the request is “GotoOtherDevice”, at step S1602 adevice name and a device address are acquired. For the GotoDesktoprequest, at step S1603 a desktop address is acquired. Then, at stepS1604 the pertinent device is added to the remote device list, and atstep S1605 a login verb is composed. When at step S1606 the type of thelogin verb is Device or Desktop, Print, Send, Delete or Reschedule, atstep S1607 the device is logged in using the corresponding login verb.When the login verb is Device or Desktop, at step S1608 the HTML pagefor the opening screen is prepared. When the login verb is Print, Send,Delete or Reschedule, at steps S1609, S1610, S1611 and S1612,respectively, HTML pages are prepared for the Print Job screen, theDelete Job screen, and the Reschedule Job screen. When the login verb isDisconnect, at step S1613 the processing for the device is logged out,and at step S1614 the pertinent device is deleted from the remote devicelist. At step S1615 the HTML page for the opening screen is prepared.And, finally, at step S1616 the HTML page is transmitted to the clientcomponent 102. The processing is thereafter terminated.

FIG. 17 is a flowchart showing the processing performed by the server103 when the request from the client component 102 is “Search”, “Help”or “Receive Job/Receive Notification”.

When at step S1701 the request is “Search”, at step S1702 a searchparameter is acquired and at step S1703 a search is performed. At stepS1704 an HTML page is prepared in accordance with the search results.For the Help request, at step S1705 a help context parameter isacquired, and at step S1706 a corresponding HTML page for a help screenis prepared. Finally, for both requests, at step S1707 the HTML pagethat is created is transmitted to the client component 102, and theprocessing is thereafter terminated.

When the request type is “Receive Job/Receive Notification”, at stepS1708 a data buffer is read. For the Receive Job request, at step S1709the contents of the buffer are transmitted for the IDAnalyze processing,which will be described while referring to FIG. 18. For the ReceiveNotification request, at step S1709 the contents of the buffer aretransmitted for the IDAnalyzeNotify processing, which will be describedwhile referring to FIG. 20. The processing is thereafter terminated.

FIG. 18 is a flowchart showing the IdAnalyze processing. During thisprocessing, a job received as row data from another device isinterpreted. This job is added to the database 104 and is executed bythe daemon module 105.

At step S1801 the Demarshal function is called to perform the demarshalcalculation, and an available buffer object is obtained. At step S1802the UnformatData function is employed to decode and develop compresseddata, and the data can be validated as units of rows. At step S1803 theDemarshal function is called again, and an available message object isobtained. Finally at step S1804 the ReceiveJob function (DUMMY), whichwill be described while referring to FIG. 19, is called, and the job isadded to the database 104.

FIG. 19 is a flowchart showing, the DUMMY processing. This module istransmitted to a CGI application, which is a dummy for an ISAPIexpansion “Receive” module that receives a row buffer transmitted bySendJob.

Actually, at step S1901 the ReceiveJob function is read from the rowbuffer received from SendJob, and at step S1902 the buffer is dumpedinto a temporary file. At step S1903 the name of this file istransmitted to IDExtn.Exe of the CGI module. At step S1904 the name ofthe file is read and data are obtained. At step S1905 this moduleemploys the Internet client call to send data to the CGI application.

FIG. 20 is a flowchart for the IdAnalyzeNotify processing. During thisprocessing, a notification that is received as row data from anotherdevice of the same type is interpreted. The notification module is addedto the processing, and the contents of the notification are performed bythe daemon module 105.

Specifically, at step S2001 the Demarshal function is called, and thedemarshal calculation is performed to obtain an available buffer object.Then, at step S2002 the UnformatData function is employed to decode anddevelop compressed data, and the available data are obtained as units ofrows. At step S2003 the Demarshal function is called again, and anavailable message object is obtained. Finally, at step S2004 theReceiveHttpNotification function, which will be described whilereferring to FIG. 21, is called and the job is added to the database104.

FIG. 21 is a flowchart showing the ReceiveHttpNotification processing.The prototype is Void CIDAction::ReceiveHttpNotification(poNotify).

This function is one used for receiving a notification transmittedaccording to the HTTP protocol. Even if the device does not support arequested notification method, the notification can be transmitted tothe destination device via an intermediate device.

At step S2101 the name and the address of a notification receiver, and anotification method are obtained. At step S2102 a check is performed todetermine whether the device is a destination device for receiving thenotification, or an intermediate device for relaying the notification toanother device.

If the device is the final destination, at step S2103 a temporary fileis created, and at step S2104 the notification message is written to thefile. At step S2105 a fixed file “pollfile” (a file polled by the daemonmodule 105) in the Windows directory is created and overwritten. At stepS2106 a command line parameter for a notification module (a module fordisplaying or creating a message) is designated in the file. And at stepS2107 the parameter is transmitted by a designated notification method.

If the device is an intermediate device, at step S2108 a check isperformed to determine whether the device has a function for issuing anotification. If the device can issue a notification, at step S2110 thedevice transmits a notification to a designated device using adesignated notification method. If the intermediate device does not havea function for issuing a notification, at step S2112 a notification inaccordance with HTTP protocol is transmitted to another intermediatedevice.

FIG. 22 is a flowchart showing the processing performed by the server103 when a request from the client component 102 is “Print”, “Send”,“Delete”, “Reschedule” or “Preview”.

Upon receiving one of these five requests, first, at step S2201 the userID, the Job ID and the Action ID are obtained.

When at step S2202 the request is “Print”, at step S2203 the time and aplace for printing are obtained, and at step S2204 a notification listis acquired. At step S2205 the PrintJob( ) function is called to performprinting.

For the Send request, at step S2206 the time and a place fortransmission are obtained, and at step S2207 a notification list isacquired. At step S2208 the SendJob( ) function is called to performtransmission.

For the Delete request, at step S2209 the CancelAction( ) function iscalled to delete a job.

For the Reschedule request, at step S2210 the RescheduleAction( )function is called to change a schedule.

For the Preview request, at step S2211 the format conversion library isemployed to convert the job into a JPG or GIF format.

For all these requests, at step S2212 a corresponding HTML page isprepared, and at step S2213 the HTML page is transmitted to the clientcomponent 102. The processing is thereafter terminated.

FIG. 23 is a flowchart showing the PrintJob processing. The prototype isVoid CIDAction::PrintJob(ActionId, NotifyList). Input parameters are theID for a designated action, and a notification setup list for a user.The job is immediately printed by the device A.

When the action ID is Print/Hold, the attributes of the action (theprinting time, a notification, etc.) are corrected to a current time anda new notification. When the action ID is Send, a new action is createdin the database 104. This depends on whether there is anotherPrintAction that relates to the job that the user is holding. When thejob is printed, the action status is “Done”, and this action is one partof the user's history.

At step S2301 a record related to a designated action is obtained toexamine the action in detail. At step S2302 a check is performed todetermine whether the previous action type is “Hold”, and at step S2303the information is stored. At step S2304 job data required for thisaction are obtained, and at step S2305 the entry in the database 104 isrevised to “Printing” because the daemon module 105 is inhibited fromperforming the action in this record.

At step S2307 or S2308, a new record is prepared, or the current recordis revised. If at step S2306 the previous action was Print/Hold, itsrecord is revised. If the previous action was Send, and if there is noPrintAction for its job that the user is holding, a new record isprepared. Then, the new/old action ID is returned (in accordance withthe condition).

At step S2309 the notification status is unconditionally changed toFalse. At step S2310 the notification is added to the new action, andthe user type is set to “Don't care” (i.e., neither a sender nor arecipient exists).

At step S2311 the job is transmitted to a print queue to performprinting using Spooler API Calls. At step S2312 the entry is revised to“Printing successful” or “Printing failure”. At step S2313 thenotification status is set in accordance with the printing status.

FIG. 24 is a flowchart showing the SendJob processing. The prototype isVoid CIDAction::SendJob(bsendjobToDatabase, ActionId, roJobMessage).

A designated “Present” job or a new job is transmitted to a designatedreceiver device list. For each transmission, a copy is obtained for eachdevice. When there are a plurality of receivers, one the copy of the jobis used by them in common. Since information for all the other devicesis also transmitted, a specific device can access the job. The HTMLprotocol is employed for the transmission of the job.

Specifically, at step S2401 a check is performed to determine whetherthe job is a job wherein the action ID is present, or a new job. Whenthe action ID is present in the job, at step S2402 the attribute of theaction is obtained, and at step S2403 a check is performed to determinewhether the action type is Hold. When the action type is Hold Job, atstep S2404 information is stored indicating that the Hold Job wasaccessed.

If at step S2405 storage of the information in the database 104 isdesignated, at step S2406 the SendJob( ) function is called, and all theinformation (a sender, a receiver, etc.) concerning the job is stored inthe database 104. At step S2407 the time is examined to determinewhether the job is to be transmitted immediately. If the job need not betransmitted immediately, the processing is terminated and thetransmission by the daemon module 105 is waited for. When the job is tobe transmitted immediately, at step S2408 the job is transmitted, andthe processing is thereafter terminated.

FIG. 25 is a flowchart showing the transmission processing performedusing the SendJob( ) function.

First, the EditAction( ) function is called to set the action status to“Active”. Then, the receiver list is processed to obtain the user'sname, the device name, and the URL address of the device. A formatconversion is performed using an appropriate image conversion librarythat corresponds to the receiver device. Message data are converted intoa byte string, which is then compressed and encoded. The obtained dataare transmitted using the HTML protocol, and the action status is set to“Done”. Furthermore, the action is included in the database 104 as onepart of the user's history, and in accordance with the transmissionstate, the notification status is set to “Success” or “Fail”. The statusindicating that the job is one in the HeldList that was accessed is set(steps S2501 to S2511).

FIG. 26 is a flowchart showing the CancelJob processing. The prototypeis Void CIDAction::CancelJob(dwActionId).

This function is employed to cancel a designated action. Specifically,at step S2601 the attribute of the action is obtained, and theCancelAction( ) function is called to set the action to “Cancel”. If atstep S2602 the action is included in the Hold list, at step S2603 it isincluded as a part of the user's history. When the action is already apart of the user's history, at step S2604 the entry is deleted. When atstep S2605 the action type is Hold, at step S2606 the notificationcondition is set to “Accessing the Hold Job”. When at step S2607 theuser is a receiver for this device, the processing is thereafterterminated. When the user is present for another device, at step S2608that device is logged in. At step S2609 the details of the action to becanceled are set, and at step S2610 the SendJob( ) function is called totransmit this information to the actual device. As a result, acancellation of the action is effected.

FIG. 27 is a flowchart showing the SendNotification processing. Theprototype is Void CIDAction::SendNotification(dwActionId).

This function is used to effect an actual notification. The transmissionof the notification type, such as Popup, is performed using the HTTPprotocol. The notification of a call or mail is performed by calling aproper module. When a method that is not supported is designated, anotification is transmitted to a designated intermediate device, whichthen re-transmits it. This function is employed only when thenotification should be transmitted “Now”. In this case, the notificationstatus is set to “Done” to prevent the daemon module 105 from pollingit.

Specifically, first, at step 82701 a notification means is examined. Ifat step S2702 the notification means is a popup window or a voicemessage, at step S2703 data are transmitted using the HTTP protocol. Ifthe notification means is a telephone, at step S2705 a check isperformed to determine whether the device possesses a notificationcapability. If the device possesses such a capability, at step S2704 thenotification is sent using the designated method. When the device doesnot possess the notification capability, at step S2706 an intermediatedevice is obtained. The intermediate device supports a designatedmechanism for issuing a notification. At step S2707 the notificationmessage and its details are transmitted to the intermediate device usingthe HTTP protocol. This method can be employed for mail, for afacsimile, and for a pager.

FIG. 28 is a diagram showing the relationship between input informationfor the server 103 and corresponding processes.

The control unit 602 handles the processes for Print Job, Send Job,Cancel Job, and Send Notification and Receive HTTP Notification. Thismodule is a main module for the back end of the printer 206, andperforms the operations “Print a job here now”, “Print a job herelater”, “Print a job at a different place now”, “Print a job at adifferent place later”, “Transmit a job to another device now, orlater”, “Change a schedule”, “Cancel the action of a job”, “Set anotification type (voice, popup window, telephone, E-mail or Fax)”,“Receive a notification”, and “Obtain or set the status for a device”.

This module covers the database module 104 so that the database 104 andcalls for it are transparent to a module (a GUI module or a daemonmodule) that employs the database 104.

FIG. 29 is a flowchart showing the processing beginning with theactivation of the daemon module 105.

The daemon module 105 constantly polls the database 104 and the files toperform an action or an operation has been registered for executionlater. The entries for these actions are prepared in the database 104.

First, at step S2901 threads for performing polling using an infiniteloop are generated, and a job to be executed “Now” is polled. When a job(action) is found in the database 104, its action type is examined(steps S2902 to S2905).

When the action type is Print, at step S2906 the PrintJob( ) function iscalled and printing is performed. When the action type is Send, at stepS2908 the ConstructSendMessage( ) function is called and a message isprepared. Then, at step S2909 the SendJob( ) function is called andtransmission of the message is performed.

When the action type is Hold, at step S2907 the CancelJob( ) function iscalled and the job is canceled.

At step S2910 the notification message is processed.

FIG. 30 is a flowchart showing the notification processing performed bythe daemon module 105.

At step S3001 the PollNotify( ) function is called to determine whethera notification message to be issued by the device is present. If such anotification message is present, at step S3002 the SendNotification( )function is called and the notification message is issued. If anotification message to be issued is not present, at step S3003 a checkis performed to determine whether an application file is present.

When at step S3004 an application file is present, at step S3005 acommand line parameter is read from the file and the file is deleted.TheShowNotify.Exe module is started through which the command lineparameter is passed.

When at step S3006 the module type is PullPrint, at step S3007 thePrintOcx.Exe file is started. When the module type is Schedule, at stepS3008 the DataDump.Exe is started.

FIG. 31 is a diagram showing the relationship between the job typeshandled by the daemon module 105 and corresponding processes.

FIG. 32 is a flowchart showing the PrintPrinterJob processing. Theprototype is IntPrintPrinterJob(pPrinterName, pDocumentName, pVoid,Bufsize).

This function is used for to notify the printer that a job is spooled.Specifically, a designated printer is opened, and notification that ajob is spooled is issued to the printer. Data are written to theprinter, and then the printer is closed (steps S3201 to S3204).

FIG. 33 is a flowchart showing the SendJob processing.

At step S3301 a check is performed to determine whether a job to betransmitted is a new one or one already present in the database 104.When the job is a new one, at step S3303 the details concerning the jobare added to the database 104. At step S3311 the sender and receiver ofthe job are also examined. When these are present in the database 104,at step S3312 a new action is added to the user's ID, and at step S3313new entries are added to the database 104 for data that are not presentin the database 104.

As for the transmission of an already existing job, the action type ofthe sender is examined. When the action type is Send and the status isTodo or Active, the Whentodo time for the action is changed to a newtime that is designated in the job message. When the action type is Sendand the action has already been performed, a new action is added to thedatabase 104. When the action type is not Send, the action entered forthe job is created in the database 104.

In all the cases, at step S3311 a check is performed to determinewhether the receiver of the job is present. When the receiver is notpresent in the database 104, at step S3313 a new entry is created. Whenthe action type is Hold (S3304) and the action status is Todo (S3306),at step S3307 the action type is changed to Send, and at step S3308 theWhentodo time is changed to a new time designated in the JobMessage.When at step S3306 the action status is not Todo, at step S3309 a newrecord for the action type Send is created, and at step S3310 theWhenTodoTime is changed to a new time designated in the JobMessage.

FIG. 34 is a flowchart showing the ReceivejobData processing.

First, at step S3400 the check item “Deny Jobs From Person/Device” isexamined. When a job is transmitted from a transmission source set inthat item, at step S3417 acceptance of the job is rejected. This item isset by a manager.

FIG. 134 is a diagram showing a setup screen for the setting up therejection of a job. In FIG. 134, the identifier for a user from whomjobs are to be rejected is set for “Deny Jobs From Person” and a devicefrom which jobs are to be rejected is set for “Deny Jobs From Device”.Then, while referring to FIG. 77, the job is rejected as will bedescribed later in the setup for a command.

The effective period and the types of processes to be rejected may beset. The thus determined check items are examined to determine whetheror not the reception of a job from a transmission source user or deviceis permitted. When the reception of a job is permitted, the receptionprocess is performed.

The job to be received is supposed to be a new one and to be aconventional job.

When a new job is received, at step S3402 a new entry is added to thedetails for the job. When at step S3403 no sender is present, at stepS3404 the entry for a sender is added. At step S3405 the details of theaction and the notifications are also added. When a sender is present,at step S3406 the details of the notification are added. If at stepS3407 no receiver is present, at step S3408 a receiver is added, and atstep S3409 the action performed by receiver is also added.

When a conventional job is received, a receiver for the job is checked.If a receiver is present and can perform the same action as thatrequired for the received job, the action status of the previous job iscanceled, and a new record is created. When the existing receiver canperform an action that differs from that for the receiver, a new entryis added for the receiver. The details contained in the notification mayalso be added. Except when the user type differs, the action status isset to Todo.

FIG. 35 is a flowchart showing the GetListOfJobAttribute processing.

All the jobs for a user at a designated place are examined, and thedetails for all the jobs are obtained. The jobs are Heldjobs andHistoryjobs. The database 104 searches for jobs for individual UserIDs,and to obtain a list, all such jobs are selected and entered in the list(steps S3501 to S3507).

FIG. 36 is a flowchart showing the PollJob processing.

A search is performed for a job for which the user type is Receiver, theaction status is Todo, and WhenTodo is shorter than the current systemtime (steps S3601 to S3605). When such a job is found, the details ofthe job are obtained and are added to the action setup, and TRUE isreturned (steps S3606 to S3608). When no such job as is described aboveis found, FALSE is returned (step S3609).

FIG. 37 is a flowchart showing the PollNotify processing.

A search is performed for a first record for which CanNotify isReceiver, WhetherToNotify is TRUE and WhenToNotify is shorter than thecurrent system time (steps S3701 to S3705). When such a record is found,the details of the notification are obtained and are added to thenotification setup, and TRUE is returned (steps S3706 to S3708). When nosuch job as is described above is found, FALSE is returned (step S3709).

FIG. 38 is a flowchart showing the CancelAction processing.

First, a search is made for a record having a designated action ID. Whensuch a record is found, a search is made for a job having the sameaction ID, and the size of the job is obtained (steps S3801 to S3804).When the job size is smaller than the JobSizeLimit set by the manager,at step S3805 the action status is examined. When the action status is“Done”, or the job size is equal to or greater than the JobSizeLimit,the action status is changed to “Deleted”, and the record is deleted(steps S3807 and S3808). In the other cases, at step S3806 the actionstatus is set to “Cancel”, and at step S3809 all notificationscorresponding to the action ID are deleted.

FIG. 39 is a flowchart showing the EditAction processing.

A search is performed for a record having a designated action ID. Whensuch a record is found, the action status is converted into a receivedparameter (steps S3901 to S3903).

FIG. 40 is a flowchart showing the EditAction processing. The prototypediffers from that explained in FIG. 39.

A search is made for a record having a designated action ID. When theaction for the pertinent record matches the action designated by theaction ID, and when the action status is Hold, the action status ischanged to a received parameter (steps S4001 to S4006). When a pertinentrecord is not found, at step S4004 a new action is added.

FIG. 41 is a flowchart showing the RescheduleAction processing.

A search is made for a record having a designated action ID. When apertinent record is found and the action status is not “Done”, Whentodois converted to received NewTime (steps S4101 to S4104).

FIG. 42 is a flowchart showing the RescheduleAction processing. Theprototype differs from that explained in FIG. 41.

At step S4201 a search is made for a record having a designated actionID. When a pertinent record is found and the UserType matches, theaction status is changed to “Cancel”, and a new record for which theaction status is Todo is added (steps S4201 to S4204). When no pertinentrecord is found, an examination is performed to determine whether a useris present. If a user is found, the UserID is obtained. If no user isfound, a new user is added and its UserID is selected, and a new actionthat corresponds to the UserID is added (steps S4206 to S4209).

FIG. 43 is a flowchart showing the RescheduleAction processing. Theprototype differs from those as explained in FIGS. 41 and 42.

A search is made for a record having a designated action ID. When apertinent record is found, the action status and the action areexamined. When the action and the action ID match, and when the actionstatus is Hold and Uncompleted, the WhenTodo time is changed to aNewTime (steps S4301 and S4302 and S4304 to S4308). When no pertinentrecord is found, at step S4303 a new action for which the action statusis Todo is added, and the WhenTodo time is changed to a NewTime.

FIG. 44 is a flowchart showing the AddNotification processing.

A new record is added to a notification, and the general information forparameters (GeneratedFromparameter) are examined to prepare a new entryconcerning this information.

FIG. 45 is a flowchart showing the AddInstruction processing.

When a ReceiveJob or a SendJob is encountered, the setup for aninstruction is called. First, at step S4501 a check is performed todetermine whether a designated UserID is present in the database 104.When the UserID is not present, the processing is thereafter terminated.When the UserID is present, at step S4502 a record is obtained from theinstruction list, and at step S4503 details for a new instruction areadded to the user ID.

The instruction is added to an instruction table in the database 104. Anassociated action and a notification provided upon receiving theinstruction are reflected in an action table and a notification table(steps S4504 and S4506).

For both the ReceiveJob and the SendJob, when instructions forgenerating these jobs are established, a record, which serves as atemplate for generating a new action and a new notification, is added tothe action table and the notification table.

FIG. 46 is a flowchart showing the GetInstruction processing.

This function is called using ReceiveJobData and SendJobData. First, atstep S4601 all the records in the instruction table are examined todetermine whether the action type is Receive or Send, and all theinstructions for the action type are obtained. At step S4602 the details(values set as instructions) contained in the JobMessage are employed todetermine whether an instruction can be executed. A check function,which will be described later, is used to examine the validity of theinstruction. When the instruction is valid, at step S4603 the ID for theinstruction is added to the list. When at step S4604 all theinstructions have been processed, a listing of the effective instructionIDs is returned.

FIG. 47 is a flowchart showing the ExecutionInstruction processing.

This function is called using ReceiveJobData and SendJobData. A searchis made for records in the action table and in the notification tables.These records are used in accordance with the instructions in theinstruction list, and copies of them are prepared for each table havinga Todo flag (set to TRUE) (steps S4701 to S4708).

The action table is searched to find a dummy action that is set inaccordance with the instruction. Based on the dummy action, a new,appropriate record is added and the action is performed.

The notification table is searched to find a dummy notification that isset in accordance with the instructions. Based on the dummynotification, a new, appropriate record is added and the notification isissued.

FIG. 89 is a flowchart showing the ResetInstruction processing. Theprototype is Void ResetInstructions(dwUserId, pInstructionList).

First, a search is made for all the commands for a designated user ID,and obtained commands and corresponding actions and notifications aredeleted (steps S8901 to S8905). Then, new commands that received areentered in the command list (step S8906).

FIG. 90 is a flowchart showing the DeleteAllInstructions processing. Theprototype is Void DeleteAllInstructions(dwUserId).

A search is made for all the commands for a designated User ID, andobtained commands and corresponding actions and notifications aredeleted (steps S9001 to S9005).

FIG. 91 is a flowchart showing the DeleteInstructions processing. Theprototype is Void DeleteInstructions(dwInstructionId).

A search is made for a command for a designated instruction ID, and theobtained command and a corresponding action and a notification aredeleted (steps S9101 to S9104).

FIG. 92 is a flowchart showing the GetInstructionDetails processing. Theprototype is Void GetInstructionDetails(dwUserId).

A search is made for commands for a designated user ID, and the obtainedcommands and a list of the details of corresponding actions andnotifications are returned (steps S9201 to S9208).

FIG. 93 is a flowchart showing Check processing. The prototype is BoolCheck(nJobChk, JobNameConnector, nDeviceChk, DeviceConnector,nPersonChk, PersonConnector, nTimeChk, TimeConnector, nStatusChk,nStatusCode).

This function is called from inside GetInstructionIds( ). A check isperformed to determine whether the command can be executed and iseffective. If the command is effective, TRUE is returned. If the commandis not effective, FALSE is returned (steps S9301 to S9303).

FIG. 94 is a flowchart showing the GetJobAttributes processing. Theprototype is Void GetJobAttributes(dwJobId, poJobMessage).

A search is made for a job having a designated job ID, the detailsconcerning the job are set in the JobMessage (steps S9401 to S9403).

FIG. 95 is a flowchart showing the GetJobAttributes processing. Theprototype is Void GetJobAttributes(dwJobId, poJobMessage).

A search is made for a job having a designated job ID, and the detailsconcerning the job are set in the JobMessage. Further, a search is madefor details concerning the sender and the receiver of the job and thedetails concerning the associated action, and these are set in theJobMessage (steps S9501 to S9505).

FIG. 96 is a flowchart showing the GetActionAttributes processing. Theprototype is Void GetActionAttributes(dwActinId, poActionMessage).

A search is made for an action having a designated action ID, and thedetails concerning the obtained action are set in the ActionMessage.Further, the names and addresses of the sender and the receiver of thejob are set in the ActionMessages for the sender and the receiver (stepsS9601 to S9605).

FIG. 97 is a flowchart showing the DeleteJob processing. The prototypeis Void Deletejob(dwUserId, dwJobId).

At step S9701 a search is made for an action for a designated UserIDhaving a designated JobID. If at step S9702 such an action is found, atstep S9703 the type of action status is examined. When the action statusis “Done”, at step S9704 the action status is changed to “Cancel”, andthe current time is set as the execution time.

When the action status is already set to “Done” or “Cancel”, at stepS9705 the action and all the associated notifications are deleted. Atstep S9706 a check is performed to determine whether there is an actionfor a UserID other than the designated UserID having the designatedJobID. If no such action is found, at step S9707 all the actions for thedesignated UserID having the designated JobID are considered to havebeen done or canceled. When there are no actions for other users and allthe actions have been done or canceled, at step S9708 the record forthis job is deleted from the job table.

FIG. 98 is a flowchart showing the GetNotificationList processing. Theprototype is Void GetNotificationList(nGeneratedFrom, dwId).

A search is made for all the notifications that were generated atdesignated generation places (either actions or instructions) and thathave designated IDs, and the details concerning the obtainednotifications are added to the list, which is then returned (steps S9801to S9804).

FIG. 99 is a flowchart showing the SetNotificationCondition processing.The prototype is Void SetNotificationCondition(nGeneratedFrom, dwId,nResult).

A search is made for a notification that was generated at a designatedplace (nGeneratedFrom) and that has a designated Id. If the obtainednotification consists of a designated value (nResult), theWhetherToNotify is set to TRUE. When the notification does not consistof a designated value, the WhetherToNotify is set to FALSE (steps S9901to S9905).

FIG. 100 is a flowchart showing the SetNotificationCondition processing.The prototype is Void SetNotificationCondition(nGeneratedFrom, dwId,bCanNotifyFlag, nDummy).

A search is made for a notification that was generated at a designatedplace and that has a designated notification ID, and CanNotifyFlag isset to a designated value (bCanNotifyFlag) (steps S10001 to S10003).

FIG. 101 is a flowchart showing the SetNotificationStatus processing.The prototype is Void SetNotificationStatus(dwNotificationId,bNotificationStatus).

A search is made for a notification having a designated notification ID,and the notification status is set to a designated value (steps S10101to S10103).

FIG. 102 is a flowchart showing the ClearHistory processing. Theprototype is Void ClearHistory( ).

First, at step S10201 the action status is examined, and actions havingthe status “Done”, “Canceled”, “Ignored” and “Deleted” are obtained. Ifat step S10203 a job has the action status “Done”, at step S10204 theexecution time for each of the obtained actions is examined. For theother jobs, at step S10205 the WhenTodo time is examined. At step S10206the obtained time is compared with the history time limit. Such a limitis set for the job by the manager. FIG. 133 is a diagram showing anexample setup screen. On this screen, the history time limit is set toone month (1 Month). When, as a result of the comparison, it is foundthat a time period equal to or longer than that set for the time limithas elapsed since the execution time or the scheduled execution time, atstep S10207 the action and the job are deleted.

FIG. 103 is a flowchart showing the DeleteAllPublicInfoJobs processing.The prototype is Void DeleteAllPublicInfoJobs( ).

A search is made for all the PublicInfojobs, and the action status isset to “Cancel” (steps S10301 to S10304).

FIG. 104 is a flowchart showing the PrintPublicInfo processing. Theprototype is Void PrintPubliclnfo(dwActionId).

A search is made for an action having a designated action ID todetermine whether there is a PublicInfoJob. When a PublicInfoJob isfound, a new action is added. The action that is so set using PublicInfothat Print is the action type, WhenTodo is the current time and Todo isthe action status (steps S10401 to S10407).

FIG. 105 is a flowchart showing the SearchData processing. The prototypeis Void SearchData(dwUserId, poSearchData).

A list is obtained of all the jobs for a designated user, and thedetails in the list are compared with the details for the Search Dataobject. When the details match, a node is added to a new list, which isthen returned (steps S10501 to S10507).

FIG. 48 is a flowchart showing the processing performed by the desktopserver component 103 in response to a request from the client component102.

At step S4801 the server component 103 receives a request from theclient component 102 and performs a corresponding process. When at stepS4802 the request is for “Login”, the login verb and the remote devicelist are acquired, and then a user password is obtained (steps S4803 andS4804). Following this, an HTML page corresponding to the user iscreated, the user password is stored, and the HTML page is transmittedto the client component 102 (steps S4805, S4806 and S4814). Theprocessing is thereafter terminated.

When the request is for “Print a File”, the user password and the nameof a file to be printed are obtained. Then an external application iscalled, and the file having the designated file name is written to aprint file employed by the application. The output print file is thenconverted into a message object, and the job is transmitted to the firstdevice on the remote device list. Finally, a corresponding HTML page iscreated and is transmitted to the client component 102 (steps S4807 toS4813 and S4814). The processing is thereafter terminated. Theprocessing performed when the request from the client component 102 is“Read Mail” or “Print Mail” will be described later while referring toFIG. 49. The processing performed when the request from the clientcomponent 102 is “View Schedule” or “Print Schedule” will be describedlater while referring to FIG. 50. The processing performed when therequest from the client component 102 is “Goto Other Device” will bedescribed later while referring to FIG. 51. And the processing performedwhen the request from the client component 102 is “Logout” or “Help”will be described later while referring to FIG. 52.

FIG. 49 is a flowchart showing the processing performed for a requestrelated to mail. This processing is employed when the request from theclient component 102 is “Read Mail” or “Print Mail”.

When the request is “Read Mail”, first, the user password for the mailserver is obtained, and a session for the reading of mail is opened.When the designated mail has been read, the session is closed (stepsS4902 to S4905).

For the request “Print Mail”, the same process is performed as for the“Read Mail” request, mail is written to a file, a Job message isgenerated, and the job is transmitted to the first device on the remotedevice list (steps S4906 to S4912).

Finally, in either case, a corresponding HTML page is generated and istransmitted to the client component 102 (steps S4913 and S4914). Theprocessing is thereafter terminated.

FIG. 50 is a flowchart showing the processing performed for a requestrelated to a schedule. This processing is performed by the desk serverwhen the request from the client component 102 is “View Schedule” or“Print Schedule”.

When the request is “View Schedule”, a check is performed to determinewhether the schedule type is “Daily” or “Monthly”, and schedule data areobtained (steps S5002 and S5003). When the request is “Print Schedule”,the same process is performed as above, the data are written to a printfile, a job message is generated, and the job is transmitted to thefirst device on the remote device list (steps S5004 to S5009).

In either case, a corresponding HTML page is generated, and istransmitted to the client component 102. The processing is thereafterterminated (steps S5010 to S5011).

FIG. 51 is a flowchart showing the processing performed for a requestrelated to another device. This processing is performed by the deskserver when the request from the client component 102 is “Goto OtherDevice”.

When the request is Goto Other Device, the name and the address of adevice are obtained. Then, the device is added to the remote device listand the login verb is generated (steps S5102 to S5104). Using the loginverb, the device is logged in, and finally a corresponding HTML page isgenerated and is transmitted to the client component 102 (S5105 toS5115). The processing is thereafter terminated. This processing is thesame as that explained while referring to FIG. 16.

FIG. 52 is a flowchart showing the processing performed for a requestrelated to logging-out or to help. This processing is performed by thedesk server when the request from the client component 102 is “Logout”or “Help”.

When at step S5201 a “Logout” request is received, at step S5202 a checkis performed to determine whether the remote device list is empty. Whenthe remote device list is empty, at step S5205, in accordance with thestatus, an OpeningScreen page is generated. When the remote device listis not empty, however, at step S5203 the next device is logged in usingthe login verb=Disconnect, and at step S5204 this next device is deletedfrom the remote device list. These processes are repeated until theremote device list has been emptied. That is, when all the devices onthe remote device list have been logged out. When the list has beenemptied, at step S5205 the OpeningScreen page is generated.

Upon receipt of a “Help” request, a help context parameter is obtained,and a corresponding help screen HTML page is generated (steps S5206 andS5207).

For both the requests, the generated HTML page is transmitted to theclient component 102, and the processing is thereafter terminated.

FIG. 53 is a flowchart showing the processing performed beginning at theinitial menu screen. FIG. 106 is a diagram showing an example initialmenu screen. When a job is present in a print queue, it is displayed onthe status screen for the initial menu. The name and the sender of thejob are displayed as job information.

At step S5301 a user selects a desired item from the initial menu. Atstep S5302 the selected item is established, and a new screen isdisplayed in accordance with the item.

First, when “Device” is selected, at step S5303 the state of the deviceis displayed. When “Back” or “Forward” is selected, at step S5304 thepreceding or the succeeding screen is displayed. When “End” is selected,at step S5305 the end process is performed.

Furthermore, when “New Interaction” is selected, at step S5306 a newprocess (login process), which will be described later while referringto FIG. 55, is initiated, and the screen is changed to a “Login” screen(FIG. 112). When “Help” is selected, at step S5307 the help screen isdisplayed.

When “Print URL” is selected, the screen is changed to a “URL print”screen (FIG. 107). When at step S5308 the URL is directly input or isdesignated by a reference and “Go” is selected, at step S5309information is obtained and previewed. At step S5310 the contents thatare confirmed are printed, and then the screen is returned to theinitial menu screen.

When “Public Info” is selected, at step S5311 program control goes tothe public information processing, which will be described later whilereferring to FIG. 54, and the screen is changed to a “public informationprocess” screen (FIG. 110).

When “Goto Device” is selected, at step S5312 a setup screen (FIG. 81)for accessing another device is displayed. Hereinafter performed is thesame process as was performed when the login verb was “Device” in theprocessing for accessing another device that was explained in FIG. 51.

A job in a print queue can also be selected on the initial screen. Toselect a job, a user touches a button displayed in front of a desiredjob name. When a specific job is selected in this manner, at step S5313a password input screen (FIG. 108) is displayed. A password is input,and when it matches the password assigned for the selected job, aprocess setup screen (FIG. 109) is displayed for the job in the printqueue that was selected.

Following this, at step S5314 an action for the job is selected, and atstep S5315 an item concerning the execution of the action is selected.When “Print later” is selected as an action, a print time can be set asthe item. A specific date (absolute date) can be set for the print time,or a relative time that must elapse following a setup time, such as“After 1 Hour”, can be set. For this setup, items such as “1 hourlater”, “2 hours later”, “6 hours later”, “Tomorrow”, “Day aftertomorrow”, “1 week later” or “2 weeks later”, are prepared and listed aschoices in a menu. When an absolute date is employed, the current dateis regarded as a default value. To select and input another date, apertinent date displayed on a calendar is touched. To select anothertime, the current time is changed.

When “Hold Here” is selected, the time for the holding period is set. Inthis case, as well as in the print data later case, the absolute date isdesignated for the holding limit, or a holding period, such as one hour(For 1 Hour), can be selected and set in the menu. To designate anabsolute date or a relative date, a touch keyboard may be displayed withwhich numerals can be directly entered, or a displayed numeral may beincremented or decremented the number of times a specific button isselected.

The action is set and is performed in accordance with theaction-associated item and the date item that are thus selected orestablished. First, when “Print later” is selected, at step S5317 aprint job is deleted from the print queue, and with the print time(absolute time) is entered in the pending job list. The screen is thenreturned to the initial menu screen, and when the setup time is reached,printing is performed.

When “Hold” is selected, at step S5318 the print job is deleted from theprint queue, and with the action “Hold” and the set holding limit isentered in the pending job list. The screen is then returned to theinitial menu screen. Thereafter, the job is held the period of timerepresented by the holding period, but will be canceled if it is notprocessed before the holding period has expired.

When “Pause/Restart Printing” is selected, at step S5319 printing istemporarily halted, the screen is returned to the initial menu screen,and the selection of “Pause/Restart Printing” (a second depression ofthe same button) is waited for. When “Cancel Printing” is selected, atstep S5320 the print job is deleted from the print queue, and “Cancel”is recorded in the history as the action taken for this job. The screenis then returned to the initial menu screen.

FIG. 54 is a flowchart showing the processing for public information.The screen shifting and the sequence for the processing are shown whenthe “Public Info” item in the initial menu screen is selected. First, atstep S5401 a public information list for the printer is displayed. FIG.110 is a diagram showing an example setup screen for a publicinformation list and for public information processing. Informationhaving an attribute called public information (a job having an actioncalled “public”) is displayed in the list, and can be printed withoutany password being required.

When at step S5402 a specific job is selected from the list, programcontrol goes to step S5405. When “From Other Device” is selected,program control goes to step S5415 to process the public informationstored in another device.

At step S5405 a process corresponding to the specific job is selected.When “Print” is selected, at step S5407 a printing place, which will bedescried later in detail in the printing process for a normal job, andthe printing time, as needed, are designated. At step S5408 the selectedpublic information is printed. When “Preview” is selected, at step S5409the previewing of data is performed, and at step S5410 the next processis selected.

If at step S5406 or S5410 “Add (Make Job Public Info. For Other Device)”is selected, another device is designated for publishing the selectedpublic information, and the selected public information is added to thepublication list for the device. FIG. 111 is a diagram showing a setupscreen for publishing the information on another device.

At step S5412 the address and the name are given of a device that isdesignated to serve as an added destination. Also designated is theperiod of time for the publication of the information. For this, as inthe previous Printing/Holding case, an absolute date may be set toconstitute the publication period, or instead, a time period may be setthat is measured from the current time. If immediate publication of theinformation is not desired, a beginning date for the publication processmay be set. In this case, a relative period, such as “1 week later”, canalso be employed. In order to limit the publication period, the perioddesignated for the publication of public information is examined beforea list of such information is displayed, and information for which thepublication period has expired is disregarded. Such a list may beexamined periodically, and information for which the publication periodhas expired can be deleted.

At step S5415 the previously described setup screen (FIG. 81) foraccessing another device is displayed, and the address and the name ofthe designated device that is to be accessed are entered. At step S5416the public information list is obtained from the accessed device and isdisplayed. Hereinafter, the same process can be performed as isperformed for a local device.

FIG. 55 is a flowchart showing the login processing performed when theperformance of a new process on the initial menu is selected. First, atstep S5501 a “Login” screen (FIG. 112) is displayed, and the user'sidentifier that has been input is examined. When the login is permitted,at step S5502 a check is performed to determine whether there are jobsavailable for the user who has logged in, i.e., pending jobs. If thereare such jobs, at step S5504 the list of jobs (FIG. 113) is displayed,and to initiate a process to perform the action, a job is selected whichwill be described later while referring to FIG. 56. If no jobs areavailable, at step S5503 the main menu (FIG. 121) is displayed and isused for the initiation of processing, a process which will be describedwhile referring to FIG. 64.

FIG. 56 is a flowchart showing the processing for selecting a job andfor performing an action. This processing is performed when a job isavailable for a user who has logged in, and at step S5601 a list ofpending jobs is displayed. FIG. 113 is a diagram showing an examplepending job list.

The pending jobs are a job that is to be printed on a specific date, ajob that is to be transmitted on a specific date, and a job that issimply to be held until a specific date has been reached (and which willbe deleted if it is not processed before the specified date). Job names,the senders or the recipients, the action types (Print, Send and Hold),and scheduled action dates are entered in the list. A variety of colorsor identifying marks that correspond to different action types areemployed for the displayed jobs so that their types can be readilyidentified. By changing their statuses to “Done” or “Canceled”, jobsthat have already been executed or that have been canceled can continuebe maintained in the history and, as needed, can be displayed in thelist with the jobs that are to be executed. It should be noted that, inthis case, the display forms of these jobs are changed in accordancewith their statuses.

At step S5602 a target job is selected, and at step S5603 a process(action) corresponding to the selected job is selected. When at stepS5604 “Main Menu” is selected, at step S5605 processing beginning at themain menu, which will be described later while referring to FIG. 64, isperformed. When “Search” is selected, at step S5606 search processing isperformed that will be described later while referring to FIG. 65. When“Print” is selected, at step S5607 the selected job is printed, whichwill be described later while referring to FIG. 60. When “Send” isselected, at step S5610 the selected job is transmitted, which will bedescribed later while referring to FIG. 62. When “Preview” is selected,at step S5608 the selected job is previewed, which will be describedlater while referring to FIG. 57. When “Delete” is selected, at stepS5609 the selected job is deleted, which will be described later whilereferring to FIG. 58. When “Schedule” is selected, at step S5611 theschedule for the selected job is changed, which will be described laterwhile referring to FIG. 59. And when “Logout” is selected, at step S5612the logout processing that was explained while referring to FIG. 52 isperformed.

FIG. 57 is a flowchart showing the selected job preview processing forpreviewing a job that is selected from the list of available jobs. Atstep S5701 a specified job is previewed. FIG. 114 is a diagram showingan example job preview screen. At step S5702 a process for the specifiedjob is selected.

When at step S5703 “Print” is selected, at step S5704 the selected jobis printed, which will be described later while referring to FIG. 60.When “Send” is selected, at step S5706 the selected job is transmitted,which will be described later while referring to FIG. 62. When “Delete”is selected, at step S5705 the selected job is deleted, which will bedescribed later while referring to FIG. 58. When “Schedule” is selected,at step S5707 the schedule for the selected job is changed, which willbe described later while referring to FIG. 59. And when “Cancel” isselected, at step S5708 the screen display is returned to that for thedisplay of the job list that was explained while referring to FIG. 56.

FIG. 58 is a flowchart showing the selected job deletion processingperformed when a job selected from the list of available jobs is to bedeleted. First, at step S5801 a job to be deleted is previewed togetherwith the identification information for the job in order to permit theuser to confirm the deletion. FIG. 115 is a diagram showing a deletionconfirmation screen. When “Delete” is selected, at step S5802 thedeletion of the job is initiated. At this time, the processing explainedin FIG. 97 is performed. Since a job to be deleted is selected from thepending job list, its action status is “Unexecuted”, whereas the statusof a deleted job is “Canceled”, which is recorded in the history for theuser. At step S5803 the screen is returned to the display of the joblist explained in FIG. 56.

FIG. 59 is a flowchart showing the processing for changing the scheduleof a selected job. This processing is performed to change the schedulefor a job selected from an available job list. At step S5901 the currentschedule, which is to be changed, is displayed. FIG. 116 is a diagramshowing a setup screen for changing the schedule. At step S5902 theschedule is changed. At step S5903 the screen is returned to the displayof the job list explained in FIG. 56.

FIG. 60 is a flowchart showing the processing for printing a selectedjob. This processing is performed to print a job that is selected fromthe available job list. At step S6001 the original action type of aselected job is determined. When the original action type is not“Print”, at step S6002 a print setup menu is displayed. FIG. 117 is adiagram showing an example print setup menu. The setup items are theplace at which printing is to be performed (a local device or anotherdevice), a device name and, if a different device is selected foremployment, its address, and the printing time.

To print using a different device, “Send” is recorded as the action typein the history for the job. When printing is initiated by a differentdevice, a Send method, which will be described later, or a Transfermethod may be employed for the transmission of data.

At step S6003 a process is selected. When at step S6004 “Print” isselected, at step S6005 the contents entered by the user are set for thedevice, and if immediate printing is instructed, the printing isinitiated. At step S6006 the screen is returned to the display of thejob list that was explained in FIG. 56. When “Preview” is selected, atstep S6007 the data are previewed, and if printing is required, programcontrol moves to step S6005. When “Notify” is selected, at step S6009 anotification is set and the screen is returned to the print setup menu.FIG. 118 is a diagram showing an example notification setup screen. Thenotification setup items are the name of a notification recipient, anotification medium (a voice message, a popup window, e-mail, atelephone, a facsimile machine, or a pager), a notification destination(an address, a telephone number, etc.), a notification trigger (at thetime of a success, at the time of a failure, at the time of accessing,etc.), and a time extending from the triggering of the notificationuntil the actual issuance of a notification. In addition, on this screencan be displayed a list of notifications, for each of which are includedthe setup contents.

FIG. 61 is a flowchart showing the processing for changing the printsetup for a selected job. In FIG. 61 the state shifting and theprocessing sequence are shown when the original action type of aselected job is “Print”.

At step S6101 a print setup change menu is displayed. FIG. 119 is adiagram showing an example print setup change menu. At step S6102 aprocess corresponding to a selected job is designated. When “Print NowAlso” is selected, at step S6104, in addition to the selected job, a jobis added for which the print time for the selected job is used as thecurrent time. When “Print Now” is selected, the print time for theselected job is changed to the current time. Therefore, in these cases,the printing is performed at the current time. When “Schedule” isselected, at step S6106 the schedule change menu in FIG. 116 isdisplayed. At step S6107 the print schedule is changed by using themenu. In either case, at step S6108 the screen is returned to thedisplay for the job list that was explained in FIG. 56.

FIG. 62 is a flowchart showing the selected job transmission processing.In FIG. 62, the state shifting and the sequence of processing are shownfor the transmission of a job that is selected from the list ofavailable jobs. At step S6201 the original action type of the selectedjob is determined. When the original action type is “Send”, thetransmission setup change processing, which will be described laterwhile referring to FIG. 63, is performed. When the original action typeis not “Send”, at step S6202 a transmission setup menu is displayed.FIG. 70 is a diagram showing an example transmission setup menu.

At step S6203 a destination and a transmission time are set and aprocess is selected. These setups are performed in the same manner as inthe printing. When at step S6204 “Send” is selected, at step S6205 aselected job is copied and the copy is transmitted. In this case, theselected job remains in the job list. When “Transfer” is selected, atstep S6206 the selected job is transferred and is deleted from the joblist. For either the transmission or the transferring of a job, at stepS6209 the screen is returned to the display of the job list that wasexplained in FIG. 56. When “Notification” is selected, at step S6207 thenotification setup screen is displayed. After the setup for thenotification has been completed, the screen is returned to thetransmission setup menu for selecting transmission or transfer.

FIG. 63 is a flowchart showing the processing for changing thetransmission setup for a selected job. In FIG. 63, are shown the stateshifting and the sequence of processing when the original action type ofa selected job is “Send”.

At step S6301 the transmission setup change menu is displayed. FIG. 71is a diagram showing an example transmission setup change menu. At stepS6302 a process for the selected job is selected. When “Send Now Also”is selected, at step S6304, in addition to the selected job, a job isadded for which the transmission time for the selected job is used asthe current time. When “Send Now” is selected, the transmission time forthe selected job is changed to the current time. Therefore, in thesecases, the transmission of a job is performed at the current time. When“Schedule” is selected, at step S6306 the schedule change menu in FIG.116 is displayed, and at step S6307 the transmission schedule is changedby using the menu. In either case, at step S6308 the screen is returnedto the display for the job list that was explained in FIG. 56. When“Notify” is selected, at step S6309 a correction menu is displayed.

FIG. 120 is a diagram showing an example correction menu. At this time,the list of transmission destinations is displayed. At step S6310 a newtransmission destination is added/designated, a transmission destinationselected from the list is corrected (deleted or changed), a process tobe performed by the transmission destination is changed, a password ischanged, and a transmission time is changed. For the setup of thenotification, at step S6312 the notification setup menu is displayed,and is then returned to the correction menu. When the notification setupis not required, the screen is returned to the transmission setup changemenu.

FIG. 64 is a flowchart showing the processing performed beginning at themain menu. In FIG. 64 is shown the screen shifting on the main menu andthe processing sequence. At step S6401 the main menu is displayed. FIG.121 is a diagram showing an example main menu. At step S6402 a process(action) is selected.

When at step S6402 “Logout” is selected, at step S6404 the logoutprocessing that was explained in FIG. 52 is performed. When “Help” isselected, at step S6405 the help processing that was explained in FIG.52 is performed. When “Search” is selected, at step S6406 the searchprocessing, which will be described later while referring to FIG. 65, isperformed. When “Print” is selected, at step S6407 the print processing,which will be described later while referring to FIGS. 67, is performed.When “Send” is selected, at step S6408 the transmission processing,which will be described later while referring to FIG. 69, is performed.When “Delete” is selected, at step S6409 the deletion processing, whichwill be described later while referring to FIG. 75, is performed. When“Set Instructions” is selected, at step S6410 the instruction setupprocessing, which will be described later while referring to FIG. 77, isperformed. When “Reschedule” is selected, at step S6411 the reschedulingprocessing, which will be described later while referring to FIG. 78.When “ADD Public Information” is selected, at step S6412 the processingfor adding public information, which will be described later whilereferring to FIG. 66, is performed. When “Goto Device” is selected, atstep S6413 the processing for accessing another device, which will bedescribed later while referring to FIG. 80, is performed. When “Goto MyDesktop” is selected, at step S6414 the processing for accessing adesktop, which will be described later while referring to FIG. 82, isperformed.

FIG. 65 is a flowchart showing the search processing performed when“Search” is selected on the main menu.

At step S6501 a search condition for searching for a job is set. A jobsetup time, an execution time, an execution state and a sender can beemployed as the search condition. Not only pending jobs but also jobsthat were executed and stored in the history are searched for.Especially when the condition where the execution state “Done” (also“Canceled”, if needed) is employed for the search, the history can bedisplayed. At step S6502 the search is initiated and a list of the jobsthat are found is displayed. At step S6503 a job is selected from thejob list, and at step S6504 a process corresponding to the selected jobis designated.

When at step S6504 “Print” is selected, at step S6506 the selected jobis printed, which was explained in FIG. 60. When “Preview” is selected,at step S6508 the selected job is deleted, which was explained in FIG.58. When “Reschedule” is selected, at step S6510 the schedule of theselected job is changed, which was explained in FIG. 59. When “MainMenu” is selected, at step S6511 the processing beginning at the mainmenu is performed, which was explained in FIG. 64.

FIG. 66 is a flowchart showing the public information additionprocessing performed when “Add Public Information” is selected. At stepS6601 a job used as public information is selected from a job list. Atstep S6602 a public information addition menu (FIG. 111) is displayed,and an added destination and a publication period are designated. Thedetails are the same as was explained for the public informationprocessing. It should be noted that a job in the user's job list is tobe published. After the designation of the details, at step S6603 theaddition of the job to the public information list is instructed, and atstep S6605 a selected job is added to the public information list. When“Cancel” is selected after the processing has been completed, at stepS6606 the screen is returned to the main menu.

FIG. 67 is a flowchart showing the printing processing performed when“Print” is selected from the main menu.

At step S6701 a place whereat a job to be printed is present isselected. FIG. 122 is a diagram showing an example menu screen forselecting a place whereat a job to be printed is present. When “Jobs onthis Device” is selected, at step S6703 the list of print jobs in thecurrent device is displayed. FIG. 123 is a diagram showing an examplemenu for selecting a job to be printed. At step S6704 a job to beprinted is selected, and at step S6705 the printing setup is performedfor a selected job. This process is performed in the same manner asexplained in FIG. 60.

When “Jobs on other Device” or “Jobs from my Desktop” is selected, atstep S6706 the address of the device is designated, and at step S6707the login screen is downloaded from the device at that address. At stepS6708 the login process is performed in accordance with the downloadedscreen. When the login is completed, since the login verb is “Print”, atstep S6710 the menu screen in FIG. 122, for selecting a job to beprinted, is downloaded to select a printing device, as is explained inFIG. 51. When a current printer is employed, at step S6711 the remoteprinting process, which will be described while referring to FIG. 68, isperformed by the printer. When the desktop is employed, at step S6712the remote printing process is performed by the desktop. When anotherdevice is employed, at step S6713 the remote printing process isperformed by that device.

FIG. 68 is a flowchart showing the remote printing processing performedby the printer. In FIG. 68 is shown the sequence of post-loginprocessing performed when printing using another device is designated onthe main menu and the designated device is the same type of printer. Theprocessing is the same as that for the printing of a job stored in thecurrent device. It should be noted that the menu and the list aredownloaded from a device that is accessed.

FIG. 69 is a flowchart showing the transmission processing. In FIG. 69are shown the screen shifting and the sequence of processing performedwhen “Send” is selected from the main menu.

At step S6901 a place, either a current device, another device or adesktop, is selected whereat a job to be transmitted is present. FIG.124 is a diagram showing an example menu screen for selecting a placewhereat a job to be transmitted is present. When “jobs on this Device”is selected, at step S6902 the job list for this device is displayed.FIG. 125 is a diagram showing an example menu for selecting a job to betransmitted. At step S6903 a job to be transmitted is selected.Hereinafter the selected job transmission processing that was explainedin FIG. 62 is performed.

When another device or a desktop is selected as a place whereat a job tobe transmitted is present, at step S6904 the address of the device isdesignated, and at step S6905 the login screen is downloaded from thedevice at that address. At step S6906 the login process is performed inaccordance with the screen. When the login is completed, since the loginverb is “Send”, at step S6908 the menu screen in FIG. 124, for selectinga job to be transmitted, is downloaded to select a transmission sourcedevice, as is explained in FIG. 51. When the printer is employed for thetransmission, at step S6909 the remote sending processing using theprinter, which will be described while referring to FIG. 72, isperformed. When the desktop is employed for the transmission, at stepS6910 the remote sending processing using the desktop is performed. Whenanother device is employed for the transmission, at step S6911 theremote sending processing using another device is performed.

FIG. 72 is a flowchart showing the remote sending processing performedby the printer. In FIG. 72 is shown the sequence of post-loginprocessing performed when transmission by another device is designatedon the main menu, and the designated device is the same type of printer.

When there is a job in the designated device, at step S7202 the list ofjobs to be transmitted is displayed. At step S7203 a job is selectedfrom the job list, and at step S7204 a process is selected. When “Send”is selected, the selected job is transmitted. This processing is thesame as the transmission of a selected job by the current device, whichwas explained while referring to FIG. 69. It should be noted that themenu and the list are downloaded from the device that is accessed.

When at step S7204 “Search” is selected, at step S7206 a new job to betransmitted is searched for. When “Logout” is selected, at step S7207the logout processing that was explained in FIG. 52 is performed. When“Main Menu” is selected, at step S7208 the screen is returned to thedisplay of the main menu.

FIG. 75 is a flowchart showing the deletion processing performed when“Delete” is selected from the main menu.

At step S7501 a place, either a current device, another device or adesktop, whereat a job to be deleted is present is selected. FIG. 73 isa diagram showing an example menu for selecting a device whereat a jobto be deleted is present. When the current device is selected, at stepS7502 the job list for this device is displayed. FIG. 74 is a diagramshowing an example list for jobs to be deleted. At step S7503 a job tobe deleted is selected. Then, the selected job is deleted in the manneras is explained in FIG. 58.

When another device or a desktop is selected as a place whereat a job tobe deleted is present, at step S7505 the address of the device isdesignated, and at step S7506 the login screen is downloaded from thedevice at that address. At step S7507 the login process is performed inaccordance with the downloaded screen. When the login is completed,since the login verb is “Delete”, the menu screen in FIG. 74 forselecting a job to be deleted is downloaded to select a job, asexplained in FIG. 51. When a job is to be deleted from the printer, atstep S7510 the remote deletion processing, which will be described whilereferring to FIG. 76, is performed by the printer. When a job is to bedeleted from the desktop, at step S7511 the remote deletion process isperformed by the desktop. When a job is to be deleted from anotherdevice, at step S7512 the remote deletion process is performed by thatdevice.

FIG. 76 is a flowchart showing the remote deletion processing performedby the printer. In FIG. 76 is shown the sequence of post-loginprocessing when the transmission from another device is designated onthe main menu and the designated device is the same type of printer.

When a job is present in the designated device, at step S7601 the joblist is displayed, at step S7602 a job to be deleted from the list isselected, and at step S7603 a process is selected. When “Delete” isselected, at step S7605 the deletion confirmation menu in FIG. 115 isdisplayed, and at step S7606 the selected job is deleted. Thisprocessing is performed in the same manner as is the deletion of theselected job in the current device, which was explained in FIG. 58. Itshould be noted that the list and the menu are downloaded from thedevice that is accessed.

When at step S7604 “Search” is selected, at step S7607 a new job to bedeleted is searched for. When “Logout” is selected, at step S7608 thelogout process explained in FIG. 52 is performed. When “Main Menu” isselected, at step S7609 the screen is returned to the main menu.

FIG. 77 is a flowchart showing the processing for setting instructions.In FIG. 77 are shown the screen shifting and the sequence of processingwhen “Set Instructions” is selected on the main menu. At step S7701 aninstruction setup screen is displayed. FIG. 126 is a diagram showing anexample instruction setup screen. On this screen, an instructionexecution condition is designated. The conditions are a job name, adevice name, a user's name, a state as a trigger for executing aninstruction (upon receipt of a job, during transmission, at the time ofprinting, upon a change in a status, etc.), an instruction effectivetime limit or period (including an infinite time), and a printer status.Furthermore, “AND” or “OR” can be also set for these conditions. Thecurrent setup is displayed as is “On receiving jobs from others”, whichis shown in FIG. 126.

When at step S7702 a process is selected, if “Take Action” is selected,at step S7704 an action is selected that is to be performed when thesetup condition is established. The printing or the holding of a job canbe selected. In addition, transmission (transfer) of a job orcancellation of a job may be selected. When “Set Notification” isselected, at step S7705 a notification is set. When “Add Instruction” isselected, at step S7706 the instruction set on the screen is validated.When “Delete” is selected, at step S7707 the instruction that is set onthe screen is deleted. Then, at step S7708 the screen is returned to themain menu. An instruction whose effective period has expired remains inthe history in addition to the jobs that have been executed. When aspecific period of time has elapsed since the expiration of the timelimit, the instruction is deleted in accordance with the managementprocess for the history.

FIG. 78 is a flowchart showing the schedule change processing performedwhen “Reschedule” is selected on the main menu.

At step S7801 a schedule change screen is displayed to select a place,either a current device, another device or a desktop, whereat a job tobe changed is present. FIG. 127 is a diagram showing an example menu forselecting a device whereat a job to be changed is present. When at stepS7802 the current device ia selected, at step S7803 the list of jobs inthe current device is displayed. FIG. 128 is a diagram showing anexample screen for selecting a job that is to be rescheduled. At stepS7804 a job to be changed is selected, and at step S7805 the schedule ofthe selected job is changed, as was explained in FIG. 59.

When another device or a desktop is selected as a place whereat a job tobe changed is present, at step S7806 the address of the device isdesignated, at step S7807 the login screen is downloaded from the deviceat the address, and at step S7808 the login process is performed inaccordance with the screen. When at step S7809 the login process iscompleted, since the login verb is “Reschedule”, at step S7810 a menuscreen in FIG. 128 for selecting a job to be rescheduled is downloadedto select a job, as explained in FIG. 51. To change the schedule of theprinter, at step S7811 the remote rescheduling process, which will bedescribed while referring to FIG. 79, is performed by the printer. Tochange the schedule for the desktop, at step S7812 the remoterescheduling process is performed by the desktop.

FIG. 79 is a flowchart showing the remote rescheduling processingperformed when rescheduling of a job for another device (same type ofprinter) is selected on the main menu.

When there is a job in the device, at step S7902 the list of all thejobs is displayed, and at step S7903 a process is selected. When a jobis selected and the rescheduling process is selected, at step S7905 ajob rescheduling screen in FIG. 116 is displayed, and the selected jobis rescheduled. This processing is performed in the same manner as isthe rescheduling of the selected job for the current device, which wasexplained in FIG. 59. It should be noted that the list and the menu aredownloaded from the device that is accessed.

When at step S7904 “Search” is selected, at step S7906 a search is madefor a new job to be rescheduled. When “Logout” is selected, at stepS7907 the logout processing explained in FIG. 52 is performed. When“Main Menu” is selected, at step S7908 the screen is returned to thedisplay of the main menu.

FIG. 80 is a flowchart showing the processing for accessing anotherdevice. In FIG. 80 is shown the sequence of the processing performedwhen an access of another device or an access of a desktop is selectedon the main menu. FIG. 81 is a diagram showing an example setup screenfor accessing another device. At step S8001 the address of the device isdesignated, and at step S8002 the login screen is downloaded from thedevice at that address. At step S8003 the login process is performed inaccordance with the downloaded screen. When at step S8004 the loginprocess is completed, since the login verb is “Device”, at step S8005the initial menu screen in FIG. 106 is downloaded to determine a deviceto be operated, as explained in FIG. 51. When a printer is to beoperated, at step S8006 the same process as is performed for the localprinter is performed for the other printer. When a desktop is to beoperated, at step S8007 the desktop processing is performed, which willbe described later while referring to FIG. 82. When another device is tobe operated, at step S8008 the process for that device is performed.

FIG. 82 is a flowchart showing the desktop processing. In FIG. 82 areshown a shift from the initial screen and the sequence of the processingperformed when “Goto My Desktop” is selected on the main menu. First, atstep S8201 the main menu is displayed. FIG. 129 is a diagram showing anexample desktop main menu. At step S8202 a process (action) is selected.

When at step S8202 “Fetch a File” is selected, at step S8204 the fileprinting process, which will be described later while referring to FIG.88, is performed. When the acquisition of new mail is selected, at stepS8205 the new mail reading processing, which will be described whilereferring to FIG. 83, is performed. When the acquisition of old mail isselected, at step S8206 the old mail acquisition processing, which willbe described later while referring to FIG. 84, is performed. When theprinting of a schedule is selected, at step S8207 the schedule isprinted. When a reference to a schedule is selected, at step S8208 theschedule reference processing is performed. When a reference to anaddress book is selected, at step S8209 the address book referenceprocessing is performed. When “Logout” is selected, at step S8210 thelogout processing explained in FIG. 52 is performed.

FIG. 83 is a flowchart showing the new mail reading processing performedwhen a user accesses his or her desktop to read new mail. At step S8300a list of new mail is displayed. FIG. 85 is a diagram showing an examplenew mail list. At step S8301 mail to be read is selected, and at stepS8302 a process for the selected mail is selected.

When at step S8302 “Main Menu” is selected, at step S8304 the screen isreturned to the main menu of the desktop. When “Open” is selected, atstep S8305 the selected mail is opened and the contents of the mail aredisplayed. FIG. 86 is a diagram showing an example display for thecontents of mail. When at step S8306 the preceding display or thesucceeding display is selected, program control returns to step S8305whereat the contents of corresponding mail are displayed. When “Print”or “Delete” is selected, mail is deleted at step S8308 or mail isprinted at step S8309. Similarly, when at step S8302 “Print” or “Delete”is selected, mail is deleted at step S8308 or mail is printed at stepS8309. When “Print All” is selected, at step S8310 all mail is printed.When “Old” (mail that has been read) is selected, the read mailacquisition processing, which will be described later while referring toFIG. 84, is performed.

During mail printing, a user accesses his or her desktop and obtains andprints mail. The printing destination can be designated as in theprevious job printing. For the printing of all the mail, a user accesseshis or her desktop to obtain and print all the mail. For the deletion ofmail, a user accesses his or her desktop to delete mail. At this time,as well as the deletion of a job, the confirmation of the deletion maybe performed.

FIG. 84 is a flowchart showing the old mail acquisition processingperformed when a user accesses his or her desktop to read old mail. Atstep S8401 a list for old mail is displayed. FIG. 87 is a diagramshowing an example list of old mail. At step S8402 mail to be read isselected, and at step S8403 a process for the selected mail is selected.

When at step S8404 “Main Menu” is selected, at step S8405 the screen isreturned to the main menu of the desktop. When “Open” is selected, atstep S8406 the selected mail is opened and the contents are displayed.FIG. 86 is a diagram showing an example display of the contents of mail.When at step S8407 the preceding display or the succeeding display isselected, program control returns to step S8406 whereat the contents ofcorresponding mail are displayed. When “Print” or “Delete” is selected,mail is deleted at step S8409 or mail is printed at step S8410.Similarly, when at step S8404 “Print” or “Delete” is selected, mail isdeleted at step S8409 or mail is printed at step S8410. When “Unread” isselected, the new mail reading processing explained in FIG. 83 isperformed.

FIG. 88 is a flowchart showing the file processing performed when a useraccesses his or her desktop to operate a file on the desktop. At stepS8801 setup is performed to obtain a file. FIG. 130 is a diagram showingan example setup screen for obtaining a file. On this screen the filename can be designated. At step S8802 a process to be performed toobtain a file is selected.

When at step S8802 “Search” is selected, at step S8803 a searchcondition is designated, at step S8804 a search is made for a file onthe desktop, and at step S8805 a list for files that correspond to thesetup condition is displayed. When at step S8802 “Show All” is selected,the list of the files in the desktop is displayed. FIG. 131 is a diagramshowing an example display for the file list for the desktop. At stepS8807 a file is selected from the search results or from the list. Whenthe file is thus selected, or when at step S8802 the file name isentered to instruct the acquisition of the file, at step S8808 thepertinent file is obtained from the desktop. At step S8809 a process forthis file is selected. FIG. 132 is a diagram showing an example screenfor selecting a process corresponding to the obtained file. When “Print”is selected, at step S8811 the obtained file is printed. When “Send” isselected, at step S8812 the obtained file is transmitted.

FIG. 137 is a flowchart showing the Logout screen creation processingperformed when Logout is the function that is commonly selected on aseries of screens following Login.

When the Logout screen creation processing is initiated, at step S13701a check is performed to determine whether a job that has not yet beenprocessed is available for a Login user. When an unprocessed job isavailable, at step S13702 a Logout screen HTML page on which is includeda job list is created and the processing is thereafter terminated. Whenno unprocessed job is available, at step S13703 a Logout screen HTMLpage on which no job list is included is created and the processing isthereafter terminated.

FIG. 138 is a flowchart showing the Logout screen processing thatcorresponds to the operation performed on the Logout screen.

FIGS. 139 and 140 are diagrams showing example Logout screens, and thescreen in FIG. 140 is obtained by scrolling the center portion in FIG.139.

When an operator enters a specific instruction on the Logout screendisplayed by the client component, a request corresponding to theinstruction is transmitted by the client component to the server, whichthen initiates the Logout screen processing in FIG. 138 that correspondsto the screen currently displayed by the client.

When the Logout screen processing is initiated, at step S13801 a requestis obtained, at step S13802 the request is analyzed, and at step S13803program control branches to a process corresponding to the request.

When Print is requested, at step S13804 a job list is printed and theprocessing is terminated. When Yes is requested, at step S13805 theLogout processing is performed, at step S13806 a screen HTML page for aprocessing menu is created, and at step S13807 the HTML page istransmitted to the client. The processing is thereafter terminated. Foranother request, at step S13809 the post-Login, general request process,which corresponds to the request that is commonly selected on a seriesof screens following Login, is performed. The processing is thereafterterminated.

As is shown in FIG. 139, job IDs are assigned to the individual jobs onthe job list, and as is shown in FIG. 140 a user ID and a contacttelephone number are described.

FIG. 141 is a flowchart showing the call response processing that isinitiated in response to the reception of a call. When an operator dialsthe contact telephone number that is described on the job list tocontact the device described in this embodiment, the call responseprocessing in FIG. 141 is initiated.

When the call response processing is started, at step S14101, a responsemessage is reproduced, such as “This is the device ABC call responsesystem. Please select ‘1’ for the state of the device, ‘2’ for anoperation for which authentication is required, and ‘#’ fortermination”. At step S14102, an operation selection entered by the useris obtained, and at step S14103 program control branches in accordancewith the type of operation requested.

For a request for the state of the device, at step S14104 the state ofthe device is obtained and at step S14105 the obtained information isreproduced. Then, program control is returned to step S14102, whereat aninstruction from the operator is received. When termination isrequested, the processing is terminated.

For processing that is related to a user's job, authentication isrequired. In this case, at step S14106, a user authentication requestmessage is reproduced, such as “Please enter user ID and depress ‘#’”.At step S14107 the operator's entry is obtained, and at step S14108program control branches in accordance with What?/an instructionreceived from the operator if the authentication is successful.

When the authentication fails, at step S14109 an authentication failuremessage is reproduced, and program control returns to step S14102 toawait an instruction from the operator.

When the authentication is successful, at step S14110 a job selectionrequest message is reproduced, such as “Please enter the job ID of adesired job and depress #”. At step S14111 a job is identified inaccordance with the job ID entered by the user. At step S14112 anoperation selection request message is reproduced, such as “Pleaseselect ‘1’ for the job state, ‘2’ for job deletion and ‘#’ fortermination”. At step S14113 the selection entered by the operator isobtained, and at step S14114 program control branches in accordance withthe operation type.

For a request for the job state, at step S14115 the state of the job isobtained, and at step S14116 the obtained information is reproduced.Then, program control returns to step S14110 to acquire an instructionentered by the user.

For the deletion of a job, at step S14117 the job is deleted and at stepS14118 the deletion results are reproduced. Program control then returnsto step S14110 to acquire an instruction entered by the operator.

For the execution of a job, at step S14119 the job is executed and atstep S14120 the execution results are reproduced. Program control thenreturns to step S14110 to acquire an instruction entered by theoperator.

For the other operation type, program control returns to step S14110 andacquires an instruction entered by the operator.

According to the embodiment described above, when a user performs adesignated process at a predetermined timing, the user can ascertainwhether there is an unprocessed job.

In addition, by querying the apparatus, the user can ascertain the stateof the device or the process, and can control the performance of theprocessing.

When New Interaction is selected on the initial menu, login is performedusing Admin (manager) and if a correct password is entered, the managermain screen is displayed. FIGS. 142A and 142B are flowcharts showing themanager main screen processing that corresponds to the operation on themanager main screen. FIG. 143 is a diagram showing an example managermain screen.

When the operator enters a specific instruction on the manager mainscreen in FIG. 143 displayed by the client component, a requestcorresponding to the operation is transmitted from the client to theserver, and the manager main screen processing in FIGS. 142A and 142B,which corresponds to the screen currently displayed by the client, isinitiated by the server.

When the manager main screen processing is initiated, at step S14201 arequest is obtained, at step S14202 it is analyzed, and at step S14203program control branches to a corresponding process.

When one of Network Settings, Resource Settings, etc., is requested, atstep S14204 a screen HTML page that corresponds to the request iscreated, and at step S14205 it is transmitted to the client. Theprocessing is thereafter terminated.

When Purge Print Queue is requested, at step S14206 all the jobs in aprint queue are deleted, and at step S14207 the owner of each of thedeleted jobs is notified the job was deleted. At step S14208 theexecution results are employed to create a screen HTML page, and at stepS14205 this page is transmitted to the client component. The processingis thereafter terminated.

When a request other than those above is entered, at step S14209 thepost-Login, general request process, which corresponds to the requestthat is commonly selected on a series of screens following Login, isperformed. The processing is thereafter terminated.

When Network Settings is selected on the manager main screen, a networksetup screen is displayed. FIG. 144 is a flowchart showing the networksetup screen processing that corresponds to the operation on the networksetup screen. FIG. 145 is a diagram showing an example network setupscreen.

When the operator enters an instruction on the network setup screendisplayed by the client component, a request corresponding to thatinstruction is transmitted from the client to the server, which theninitiates the network setup screen processing in FIG. 144 thatcorresponds to the operation screen currently displayed by the client.

It should be noted, however, that the input operation for setting up theHost Name, IP Address, Net Mask, Default Gateway, DNS Domain Name, DNSServer and WINS Server is completed only through the client processing,without the server processing in FIG. 144 being started. Since Set &Reboot, Cancel, or other operations require the server processing, thenetwork setup screen processing in FIG. 144 is started.

When the network setup screen is initiated, at step S14401 a request isobtained, at step S14402 it is analyzed and at step S14403 programcontrol branches to a corresponding process.

When Set & Reboot is requested, at step S14404 network parameters areset for the Host Name, IP Address, Net Mask, Default Gateway, DNS DomainName, DNS Server and WINS Server that have been set by the client, andat step S14405 the system is re-activated to validate the setup of thenetwork parameters. The processing is thereafter terminated.

When Cancel is requested, at step S14406 the preceding screen HTML pageis created, and at step S14407 it is transmitted to the client. Theprocessing is thereafter terminated.

For another request, at step 514408 the post-Login, general requestprocess, which corresponds to the request that is commonly selected on aseries of screens following Login, is performed, and the processing isthereafter terminated.

FIG. 146 is a flowchart showing the job setup screen processing thatcorresponds to the operation on the job setup screen, which is displayedwhen Job Settings is selected on the manager main screen. FIG. 147 is adiagram showing an example job setup screen.

When the operator enters an instruction on the job setup screen in FIG.147 that is displayed by the client, a request that corresponds to theoperation is transmitted from the client to the server, which thenbegins the job setup screen processing in FIG. 146 that corresponds tothe operation screen currently displayed by the client.

In this processing, the following can be set: Default Hold Time (theinitial value of a time period during which a designated job is held),History Time Limit (the time limit for holding a job that was executedand is stored as history), Maximum Time For Rescheduling Jobs (a timeperiod during which a designated execution time for a job can bechanged), Job Size Limit (the maximum size of a job) and DefaultProtocol (the initial protocol value).

It should be noted, however, that the input operation for the setup ofDefault Hold Time, History Time Limit, Maximum Time For ReschedulingJobs, Job Size Limit, Deny Jobs From Person and Deny Jobs From Devicesis completed only through client processing, without the serverprocessing in FIG. 146 being required. Since the OK, Cancel and otheroperations require the server processing, the job setup screenprocessing in FIG. 146 is performed.

When the job setup screen processing is begun, at step S14601 a requestis obtained, at step S14602 it is analyzed and at step S14603 programcontrol branches to a corresponding process.

When OK is requested, at step S14604 the job setup parameters are setfor Default Hold Time, History Time Limit, Maximum Time For ReschedulingJobs, Job Size Limit, Deny Jobs From Person and Deny Jobs From Devicesthat are set by the client. At step S14605 the preceding screen HTMLpage is created and at step S14606 it is transmitted to the client. Theprocessing is thereafter terminated.

When Cancel is requested, at step S14605 the preceding screen HTML pageis created and at step S14606 it is transmitted to the client. Theprocessing is thereafter terminated.

For the other request, at step S14607 the post-Login, general requestprocess, which corresponds to the request that is commonly selected on aseries of screens following Login, is performed, and the processing isthereafter terminated.

FIG. 148 is a flowchart showing the resource setup screen processingthat corresponds to the operation on a resource setup screen, which isdisplayed when Resource Settings is selected on the manager main screen.FIG. 149 is a diagram showing an example resource setup screen.

When the operator enters an instruction on the resource setup screen inFIG. 149 that is displayed by the-client, a request corresponding to theinstruction is transmitted from the client to the server, which theninitiates the resource setup screen processing that corresponds to theoperation screen currently displayed by the client.

When a voice modem is installed, its telephone number is input. When avoice modem is not installed, Use Proxy is selected to use anotherdevice that includes a voice modem. The processing performed when UseProxy is selected will be described later while referring to FIG. 150.

It should be noted, however, that the input operation for the setting ofVoice Modem Installed is completed only through client processing,without the server processing in FIG. 148 being required. Since theoperations for Set, Cancel, Use Proxy, E-mail Configure, Fax Configureand the other operation require server processing, the resource setupscreen processing in FIG. 148 is performed.

When the resource setup screen processing is initiated, at step S14801 arequest is obtained, at step S14802 it is analyzed and at step S14803program control branches to a corresponding process.

When Set is requested, at step S14804 the resource setup parameters areset for the Voice Modem Installed, E-mail Capabilities and FaxCapabilities that are set by the client. At step S14805 the precedingscreen HTML page is created and at step S14806 it is transmitted to theclient. The processing is thereafter terminated.

When Cancel is requested, at step S14805 the processing screen HTML pageis created and at step S14806 it is transmitted to the client. Theprocessing is thereafter terminated.

When Use Proxy, E-mail Configure or Fax Configure is requested, at stepS14807 a screen HTML page corresponding to the request is created and atstep S14806 it is transmitted to the client. The processing isthereafter terminated.

For a request other than those, at step S14808 the post-Login, generalprocessing, which corresponds to the request that is commonly selectedon a series of screens following Login, is performed. The processing isthereafter terminated.

When Use Proxy is selected on the resource setup screen, a modem proxysetup screen is displayed. FIG. 150 is a flowchart showing the modemproxy setup screen processing that corresponds to a modem proxy setupscreen. FIG. 151 is a diagram showing an example modem proxy setupscreen.

When the operator enters an instruction on the modem proxy setup screendisplayed by the client component, a request corresponding to theinstruction is transmitted from the client to the server, which thenbegins the modem proxy setup screen processing that corresponds to theoperation screen currently displayed by the client.

In this embodiment, a maximum of three devices, Proxy devices 1 to 3,can be designated using the device name and the address. It should benoted, however, that the input operation for the setting of Proxydevices 1 to 3 is completed only through client processing without theserver processing in FIG. 142 being required. Since the OK, Cancel andother operations require the server processing, the modem proxy setupscreen processing in FIG. 150 is performed.

When the modem proxy setup screen processing is initiated, at stepS15001 a request is obtained, at step S15002 it is analyzed, and at stepS15003 program control branches to a corresponding process.

When OK is requested, at step S15004 the modem proxy setup parametersare set for the Proxy devices 1 to 3 that are set by the client. At stepS15505 the preceding screen HTML page is created and at step S15006 itis transmitted to the client. The processing is thereafter terminated.

When Cancel is requested, at step S15505 the preceding screen HTML pageis created and at step S15006 it is transmitted to the client. Theprocessing is thereafter terminated.

For another request, at step S15007 the post-Login; general requestprocessing, which corresponds to the request that is commonly selectedon a series of screens following Login, is performed. The processing isthereafter terminated.

FIG. 152 is a flowchart showing the other setup screen processing thatcorresponds to the other setup screen displayed when Miscellaneous isselected on the manager main screen. FIG. 153 is a diagram showing anexample of the other setup screen.

When the operator enters an instruction on the other setup screen thatis displayed by the client, a request corresponding to the instructionis transmitted from the client to the server, which then begins theother setup screen processing in FIG. 152 that corresponds to theoperation screen currently displayed by the client.

It should be noted, however, that the input operation for the setting ofTime Out Duration and Voice Prompt is completed only through clientprocessing without the server processing in FIG. 10 being required.Since the Set, Cancel and other operations require the serverprocessing, the other setup screen processing in FIG. 152 is begun.

When the other setup screen processing is initiated, at step S15201 arequest is obtained, at step S15202 it is analyzed and at step S15203program control branches to a corresponding process.

When Set is requested, at step S15204 the other setup parameters are setfor the Time Out Duration and Voice Prompt that have been set by theclient. At step S15205 the processing screen HTML page is created and atstep S15206 it is transmitted to the client. The processing isthereafter terminated.

When Cancel is requested, at step S15205 the preceding screen HTML pageis created and at step S15206 it is transmitted to the client. Theprocessing is thereafter terminated.

For the other request, at step. S15207 the post-Login, general process,which corresponds to the request that is commonly selected on a seriesof screens following Login, is performed and the processing isthereafter terminated.

FIG. 154 is a flowchart showing the password setup screen processingthat corresponds to a password setup screen displayed when ChangePassword is selected on the manager main screen. FIG. 155 is a diagramshowing an example password setup screen.

When the operator enters an instruction on the password setup screendisplayed by the client, a request corresponding to the operation istransmitted from the client to the server, which then begins thepassword setup screen processing in FIG. 154 that corresponds to theoperation screen currently displayed by the client.

It should be noted, however, that the input operations for the settingof New Admin Password, Reconfirm Admin Password, New Shutdown Passwordand Reconfirm Password are completed only through client processing,without the server processing in FIG. 19 being required. Since the OK,Cancel and the other operations require the server processing, thepassword setup screen processing in FIG. 154 is performed.

When the password setup screen, processing is initiated, at step S15401a request is obtained, at step S15402 it is analyzed, and at step S15403program control branches to a corresponding process.

When OK is requested, at step S15404 the password setup parameters areset for the New Admin Password, Reconfirm Admin Password, New ShutdownPassword and Reconfirm Shutdown Password that were set by the client. Atstep S15405 the preceding screen HTML, page is created and at stepS15406 it is transmitted to the client. The processing is thereafterterminated.

When Cancel is requested, at step S15405 the preceding screen HTML pageis created and at step S15406 it is transmitted to the client. Theprocessing is thereafter terminated.

For the other request, at step S15407 the post-Login, generalprocessing, which corresponds to the request that is commonly selectedon a series of screens following Login, is performed. The processing isthereafter terminated.

FIG. 156 is a flowchart showing the public information deletion screenprocessing that corresponds to the operation on the public informationdeletion screen displayed when Delete Public Info. is selected on themanager main screen. FIG. 157 is a diagram showing an example publicinformation deletion screen.

When the operator enters an instruction on the public informationdeletion screen in FIG. 157 that is displayed by the client, a requestcorresponding to the instruction is transmitted from the client to theserver, which then begins the public information deletion processingthat corresponds to the operation screen currently displayed by theclient.

It should be noted, however, that the input operation for designatingtarget public information is completed only through client processing,without the server processing in FIG. 156 being required. Since theDelete, Delete All, Cancel and other operations require the serverprocessing, the public information deletion screen processing in FIG.156 is performed.

When the public information deletion screen processing is initiated, atstep S15601 a request is obtained, at step S15602 it is analyzed and atstep S15603 program control branches to a corresponding process.

When Delete is requested, at step S15604 the public informationdesignated by the client is deleted. At step S15605 the screen HTML pageof the updated public information list is created, and at step S15608 itis transmitted to the client. The processing is thereafter terminated.

When Delete All is requested, at step S15606 all the public informationis deleted. At step S15607 the preceding screen HTML page is created andat step S15608 it is transmitted to the client. The processing isthereafter terminated.

When Cancel is requested, at step S15607 the preceding screen HTML pageis created and at step S15608 it is transmitted to the client. Theprocessing is thereafter terminated.

For the other request, at step S15609 the post-Login, general requestprocess, which corresponds to the request that is commonly selected on aseries of screens following Login, is performed. The processing isthereafter terminated.

FIG. 158 is a flowchart showing the job database management screenprocessing that corresponds to the operation on a job databasemanagement screen displayed when Job Administration is selected on themanager main screen. FIG. 159 is a diagram showing an example databasemanagement screen.

When the operator enters an instruction on the job database managementscreen displayed by the client, a request corresponding to theinstruction is transmitted from the client to the server, which theninitiates the job database management screen processing that correspondsto the operation screen currently displayed by the client.

It should be noted, however, that the input operations for designatingInitialize Database, Repair Database and Compact Database are completedonly through client processing, without the server processing in FIG.158 being required. Since the Proceed, Cancel and other operationsrequire the server processing, the job database management screenprocessing in FIG. 158 is performed.

When the job database management screen processing is initiated, at stepS15801 a request is obtained, at step S15802 it is analyzed, and at stepS15803 program control branches to a corresponding process.

When Proceed is requested, at step S15804 a process designated by theclient is performed, and the processing is terminated.

When Cancel is requested, at step S15805 the preceding screen HTML pageis created, and at step S15806 it is transmitted to the client. Theprocessing is thereafter terminated.

For the other request, at step S15807 the post-Login, general process,which corresponds to the request that is commonly selected on a seriesof screens following Login, is performed. The processing is thereafterterminated.

FIG. 160 is a flowchart showing the shutdown screen processing thatcorresponds to the operation on a shutdown screen displayed when ShutDown is selected on the manager main screen. FIG. 161 is a diagramshowing an example shutdown screen.

When the operator enters an instruction on the shutdown screen displayedby the client, a request corresponding to the instruction is transmittedfrom the client to the server, which then begins the shutdown screenprocessing in FIG. 160 that corresponds to the operation screencurrently displayed by the client.

When the shutdown screen processing is begun, at step S16001 a requestis obtained, at step S16002 it is analyzed, and at step S16003 programcontrol branches to a corresponding process.

When Yes is requested, at step S16004 the shutdown process is performed,and the processing is terminated.

When Cancel is requested, at step S16005 the preceding screen HTML pageis created and at step S16006 it is transmitted to the client. Theprocessing is thereafter terminated.

When Help is requested, at step S16007 a Logout Help screen HTML page iscreated and at step S16006 it is transmitted to the client. Theprocessing is thereafter terminated.

For the other request, at step S16008 the post-Login, general requestprocess, which corresponds to the request that is commonly selected on aseries of screens following Login, is performed. The processing isthereafter terminated.

According to the above described embodiment, since the manager canperform a process that a common user can not, the apparatus can becontrolled by the manager.

The present invention may be applied for an apparatus constituted by asingle device, or for a system constituted by a plurality ofapparatuses. For implementing the present invention, a memory medium onwhich is stored software program code for implementing the functions inthe above embodiment may be supplied to an apparatus or to a system, andthe computer in the apparatus or in the system may read the program codefrom the memory medium.

In addition, the scope of the present invention includes not only a casewhere the functions in the embodiment can be performed when program codeis read and executed by the computer, but also a case where, inaccordance with an instruction in the program code, an OS running on thecomputer, etc., can perform the processing required to accomplish thefunctions included in the above embodiment.

The memory medium on which such program code is recorded constitutes thepresent invention.

Although the present invention has been described in its preferred formwith a certain degree of particularity, many apparently widely differentembodiments of the invention can be made without departing from thespirit and the scope thereof. It is to be understood that the inventionis not limited to the specific embodiments described herein, except asdefined in the appended claims.

What is claimed is:
 1. An information processing apparatus comprising:transmission means for transmitting object information that is to beprocessed; object information storage means for storing said objectinformation that is to be processed; display means for displaying, as alist, said object information that is stored in said object informationstorage means; object information selection means for selecting objectinformation from said list of object information; destinationdesignation means for designating a transmission destination for saidobject information that is to be processed; transmission methodselection means for selecting a first transmission method or a secondtransmission method; and control means for, when said first transmissionmethod is selected by said transmission method selection means,permitting said transmission means to copy from said object informationstorage means said object information selected by said objectinformation selection means, and, when said second transmission methodis selected by said transmission method selection means, for permittingsaid transmission means to extract, from said object information storagemeans, said object information that is selected by said objectinformation selection means, and to transmit said object information tosaid transmission destination that is designated by said transmissiondesignation destination means.
 2. An information processing apparatusaccording to claim 1, wherein said object information storage meansstores object information before execution of said object informationhas been performed.
 3. An information processing apparatus according toclaim 2, wherein said object information storage means stores a type ofprocess in conjunction with object information.
 4. An informationprocessing apparatus according to claim 3, wherein said objectinformation storage means stores, as different process types,transmission processes that respectively use said first transmissionmethod and said second transmission method.
 5. An information processingapparatus according to claim 1, further comprising: password setup meansfor setting a password for object information.
 6. An informationprocessing apparatus according to claim 5, wherein said destinationdesignation means designates a plurality of recipients, and saidpassword setup means establishes a unique password for each of saidplurality of recipients.
 7. An information processing apparatusaccording to claim 1, further comprising: process setup means forsetting up a process that said transmission destination is to performfor said object information.
 8. An information processing apparatusaccording to claim 7 wherein said process setup means sets a time atwhich said transmission destination will perform a process.
 9. Aninformation processing method comprising: a display step of displaying,as a list, object information that is to be processed, which is storedin an object information storage unit for storing said objectinformation that is to be processed; an object information selectionstep of selecting object information from said list of objectinformation; a destination designation step of designating atransmission destination for said object information that is to beprocessed; a transmission method selection step of selecting a firsttransmission method or a second transmission method; and a transmissionstep of, when said first transmission method is selected at saidtransmission method selection step, copying from said object informationstorage unit said object information selected at said object informationselection step, and of, when said second transmission method is selectedat said transmission method selection step, extracting from said objectinformation storage unit said object information that is selected atsaid object information selection step, and transmitting said objectinformation to said transmission destination that is designated at saidtransmission designation destination step.
 10. An information processingmethod according to claim 9, wherein said object information storageunit stores object information before execution of said objectinformation has been performed.
 11. An information processing methodaccording to claim 10, wherein said object information storage unitstores a type of process in conjunction with object information.
 12. Aninformation processing method according to claim 11, wherein said objectinformation storage unit stores, as different process types,transmission processes that respectively use said first transmissionmethod and said second transmission method.
 13. An informationprocessing method according to claim 9, further comprising: a passwordsetup step of setting a password for object information.
 14. Aninformation processing method according to claim 13, wherein a pluralityof recipients are designated at said destination designation step, and aunique password for each of said plurality of recipients is establishedat said password setup step.
 15. An information processing methodaccording to claim 13, wherein a time at which said transmissiondestination will perform a process is set at said process setup step.16. An information processing method according to claim 9, furthercomprising: a process setup step of setting up a process that saidtransmission destination is to perform for said object information. 17.A storage medium on which is stored a program for implementing an imageprocessing method, said method comprising: a display step of displaying,as a list, object information that is to be processed, which is storedin an object information storage unit for storing said objectinformation that is to be processed; an object information selectionstep of selecting object information from said list of objectinformation; a destination designation step of designating atransmission destination for said object information that is to beprocessed; a transmission method selection step of selecting a firsttransmission method or a second transmission method; and a transmissionstep of, when said first transmission method is selected at saidtransmission method selection step, copying from said object informationstorage unit said object information selected at said object informationselection step, and when said second transmission method is selected atsaid transmission method selection step, extracting from said objectinformation storage unit said object information that is selected atsaid object information selection step, and transmitting said objectinformation to said transmission destination that is designated at saidtransmission designation destination step.
 18. An information processingapparatus comprising: transmission means for transmitting objectinformation that is to be processed; object information storage meansfor storing said object information in conjunction with a correspondingexecution time and a corresponding transmission destination; displaymeans for displaying as a list object information that is stored in saidobject information storage means; object information selection means forselecting object information from said list of object information;change means for changing a setup that is stored in said objectinformation storage means in conjunction with said object informationselected by said object information selection means; and control meansfor permitting said transmission means to transmit said objectinformation, which is stored in said object information storage meanswith said corresponding execution time and said correspondingtransmission destination, to said transmission destination and at saidexecution time.
 19. An information processing apparatus according toclaim 18, wherein said change means changes said execution time to anexecution time for immediate execution for said selected objectinformation.
 20. An information processing apparatus according to claim18, further comprising: time designation means for designating a time,wherein said change means changes said execution time to said time thatis designated by said time designation means for said selected objectinformation.
 21. An information processing apparatus according to claim18, further comprising: addition means for, instead of changing saidexecution time for said selected object information, adding to saidobject information storage means a process to be carried out for saidselected object information at a time different from said executiontime.
 22. An information processing apparatus according to claim 21,wherein said addition means adds a process for immediately executingsaid selected object information.
 23. An information processingapparatus according to claim 21, further comprising: time designationmeans for designating a time, wherein said addition means adds a processfor executing said selected object information at the time designated bysaid time designation means.
 24. An information processing apparatusaccording to claim 18, whereby said change means cancels processing forsaid selected object information.
 25. An information processingapparatus according to claim 24, further comprising: history storagemeans for storing a history of execution of object information, wherein,when execution of said selected object information is canceled by saidchange means, a cancellation history is stored in said history storagemeans.
 26. An information processing apparatus according to claim 18,wherein said change means changes said transmission destination for saidselected object information.
 27. An information processing apparatuscomprising: object information storage means for storing objectinformation to be processed; object information list display means fordisplaying as a list object information stored in said objectinformation storage means; object information selection means forselecting object information that is to be published; setup means forsetting a publication time limit; and published information registrationmeans for registering as published information, in conjunction with saidpublication time limit that is set by said setup means, said objectinformation in said published information storage means that is selectedby said selection means.
 28. An information processing apparatusaccording to claim 27, further comprising: determination means fordetermining whether an allocated publication time has expired for acorresponding object information stored in said published informationstorage means; publication list display means for displaying as a listpublished information for which said determination means has determinedthat said allocated publication time has not expired; publishedinformation selection means for selecting published information fromsaid list displayed by said publication list display means; and outputmeans for outputting contents of said published information selected bysaid published information selection means.
 29. An informationprocessing apparatus according to claim 28, wherein said publishedinformation storage means is provided for a different device, furthercomprising: device selection means for selecting said different device;and communication means for communicating with said device that has beenselected by said device selection means.
 30. An information processingapparatus according to claim 29, wherein, to select said differentdevice, said device selection means employs an address and a name ofsaid different device.
 31. An information processing apparatus accordingto claim 27, wherein said setup means designates a print time using anabsolute date.
 32. An information processing apparatus according toclaim 31, wherein said setup means includes: calendar display means fordisplaying a calendar; and date selection means for selecting a dateincluded on said calendar displayed by said calendar display means, andwherein said setup means designates, as said print time, said dateselected by said date selection means.
 33. An information processingapparatus according to claim 27, wherein said setup means designates aprint time using a relative date.
 34. An information processingapparatus according to claim 33, wherein said setup means includes: menudisplay means for displaying a menu; and item selection means forselecting an item from said menu displayed by said menu display means,and wherein said setup means designates, as an end date for saidallocated publication time, a date that corresponds to said itemselected by said item selection means.